Ask a compliance question

12207 1/ ISO/IEC 12207 1/ N/A NATO STANAG 4427 1/, 2/ NATO ACMP-2100 1/ Guidance, Including Handbooks DELETED MIL-HDBK-61 GEIAHB6493/ ISO 10007 1/ NIST SP 800-128 1/ NATO STANAG 4427 1/, 2/ NATO ACMP-2009 1/ FOOTNOTES: 1/ Not extensively covered in MIL-HDBK-61. 2/ Strictly speaking, a Standard NATO Agreement (STANAG) is not a standard, but rather an agreement to use standards, and other documents, that are listed in body of STANAG. 3/ Adopted by DoD, but use not mandated in policy. NOTE: Titles of documents in table are as follows: DELETED DoDD 5000.01, The Defense Acquisition System DoDI 5000.02, Operation of the Adaptive Acquisition Framework DoDI 5000.88 Engineering of Defense Systems SAE EIA-649, Configuration Management Standard SAE EIA-649-1, Configuration Management Requirements for

RE C-1. TMRR phase – Continued. Source: https://assist.dla.mil -- Downloaded: 2026-07-20T01:48Z Check the source to verify that this is the current version before use. MIL-HDBK-61B w/CHANGE 1 APPENDIX C 61 ACTIVITY: Management and Planning Actions Benefits/Risks Government Develop concept of operation and acquisition strategy CM Prepare, coordinate, and release procedures implementing the Government CM process; conduct training. (See Govt. configuration identification, control, and status accounting activities below.) Measure and evaluate contractor CM process Government and Contractor Jointly participate in program management and systems engineering IPTs Prepare and coordinate configuration management plans Define digital data interface and data requirements Effect process improvem

stipulated by statute or policy, program managers should consider whether the use of standards on their program is beneficial in establishing and maintaining an efficient and effective CM process. In order to mitigate program cost, schedule, and technical risk, this revision to MIL-HDBK-61 is being issued to provide up-to-date guidance on applying CM requirements on DoD acquisition contracts. Appendix C provides recommendations for selection and tailoring of CM elements to be applied by program type. 5. Comments, suggestions, or questions on this document should be addressed to Commander, Naval Sea Systems Command, ATTN: SEA 05S, 1333 Isaac Hull Avenue, SE, Stop 5160, Washington Navy Yard DC 20376-5160 or emailed to CommandStandards@navy.mil, with the subject line “Document Comment”. Sinc

information is acceptable. This type substitution does not require submission of engineering change proposals, deviations, or waivers in accordance with MIL-HDBK-61. 4.2 Commercial parts. When the equipment design specifies a commercial part, a defense specification part may be substituted when the form, fit, and functional characteristics of the standard part are equal to, or better than, those of the specified commercial part under equivalent environmental conditions. Substitutions are subject to applicable configuration control procedures of MIL-HDBK-61. 4.3 Unavailable parts. When the equipment design specifies a part that is unavailable, a substitute part which meets the form, fit, and functional characteristics of the specified part may be substituted after approval is obtained from

range safety certification report – Continued. Source: https://assist.dla.mil -- Downloaded: 2026-07-20T01:50Z Check the source to verify that this is the current version before use. MIL-HDBK-828D APPENDIX B 60 6. Controls for protection from reflected laser beams: 7. Recommended training: 8. Recommended pre-briefs for: a. Laser users: b. Laser Range Personnel FIGURE B-3. Laser range safety certification report – Continued. Source: https://assist.dla.mil -- Downloaded: 2026-07-20T01:50Z Check the source to verify that this is the current version before use. MIL-HDBK-828D APPENDIX B 61 Laser Range Certification 1. (range/range training facility) and attendant laser hazard analysis have been designated to accommodate the following, under the supervision of a qualified laser range officer in

(average of 10 thunderstorm days per year), only 175 transients are expected to occur in a 10-year period. Transient occurrence and amplitudes may be as listed in Table 1-10. 1-60 Source: https://assist.dla.mil -- Downloaded: 2026-07-20T01:54Z Check the source to verify that this is the current version before use. Figure 1-36. MIL-HDBK-419A 1-61 1 Source: https://assist.dla.mil -- Downloaded: 2026-07-20T01:54Z Check the source to verify that this is the current version before use. MIL-HIIBK-419A Figure 1-37. Secondary AC Surge Arrester Installation, Ungrounded Service 1-62 Source: https://assist.dla.mil -- Downloaded: 2026-07-20T01:54Z Check the source to verify that this is the current version before use. MIL-HDBK-419A Table 1-9. Transient Occurrences, High-Incident Lightning Areas Transi

are usually recorded in the hit/miss format for manual inspections, and may be in the â vs a format for automated readers. The data are analyzed using the new mh1823 POD software, Appendix G. Source: https://assist.dla.mil -- Downloaded: 2026-07-20T01:50Z Check the source to verify that this is the current version before use. MIL-HDBK-1823A APPENDIX D 60 THIS PAGE INTENTIONALLY BLANK Source: https://assist.dla.mil -- Downloaded: 2026-07-20T01:50Z Check the source to verify that this is the current version before use. MIL-HDBK-1823A APPENDIX E 61 Appendix E – Test Program Guidelines E.1 SCOPE E.1.1 Scope This appendix presents the test program procedures of a Nondestructive Evaluation (NDE) demonstration. The purpose of an NDE demonstration is to produce POD(a) curve with 95% confidence bou

Federated Assurance Center portal [https://jfac.navy.mil]. (b) (Added)(DAF) Software security testing should be conducted in a development and test environment (see Military Handbook 61 Revision B (MIL-HDBK 61 Rev B, Department of Defense Handbook: Configuration Management Guidance) with SECTION 3: PROCEDURES 23DoDI5000.87_DAFI63-150 11 AUGUST 2021 vulnerabilities mitigated following AFI 17-101, Risk Management Framework (RMF) for Air Force Information Technology (IT) Systems, before a system is made operational. (T-1) Consider including security technical implementation guide (STIG) usage and vendor hardening guidance when using memorandum of agreements or service level agreements following DoDI 4000-19, Support Agreements, as implemented in Air Force Policy Directive (AFPD) 25-2, Support