DI-ENVR-82096
Hardness Data Manual (HDM) Update
The Hardness Data Manual (HDM) Update DID specifies the format and content preparation instructions for updating an existing Hardness Data Manual to reflect hardness-related hardware changes on a contract.
Approval DateDecember 9, 2016
AMSC NumberF9758
Preparing ActivityAF-27
Project NumberENVR-2016-004
OPR—
DTIC Applicable—
GIDEP ApplicableNo
Limitation—
Applicable FormsNone
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Application & Interrelationship
—
Use & Relationship
This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements as delineated in the contract according to MIL-STD-1766C, 5.5.3.6.
This DID is applicable to system development contracts during the engineering and manufacturing development and production phases, and to other contracts where changes to hardness critical hardware are being made and that hardware has an existing Hardness Data Manual.
This DID is the original release (new). Comments, suggestions, or questions on this document should be addressed to the Defense Standardization Program Office (DSPO), 1551 Wyoming Blvd. SE Kirtland AFB, NM 87117-5624 or emailed to [email protected]. Since contact information can change, you may want to verify the currency of this address information using the ASSIST online database at https://assist.dla.mil.
Preparation Instructions
1Format.The report and all attachments shall be provided in Microsoft Word but follow the format of the existing Hardness Data Manual (HDM) that is being updated. Page size shall be 8 1/2 x 11 inches except where necessary, 11 x 17 inches may be used as a foldout. Security classification and distribution markings shall conform to the requirements of the contract, when applicable.
2Reference documents.Use version applicable on the data of contract award (which may require updating of links provided below).
2.1SAE / EIA-649_1 Configuration Management Requirements for Defense Contracts(http://standards.sae.org/eia649_1/).
2.2DD Form 1696 - Specification Change Notice(www.dtic.mil/whs/directives/forms/eforms/dd1696.pdf).
2.3AF Form 3925 - Engineering Order(http://static.epublishing.af.mil/production/1/afmc/form/afmc3925/afmc3925.pdf).
2.4AF Form 3926 - Engineering Order (continuation)(http://static.epublishing.af.mil/production/1/afmc/form/afmc3926/afmc3926.pdf).
3Content.The report content shall preserve the existing HDM format and be as follows:
3.1Title PageUpdate the revision information and date to reflect the current update.
3.2Table of ContentsFollow the existing format but add new content relevant to the current program and delete items for hardware that is no longer relevant.
3.3Update the Introduction, Physical and FunctionDescriptions, References Section, Hardness Critical Item List/Index, Hardness Requirements, Assessment, Design Criteria, Design Features, Hardness Design Evaluation, and Hardness Design Proof with content applicable to the current contract. Provide complete details that demonstrate the new hardware meets the requirements. The detailed tasks of MIL-STD-1766C, Section 5, provide insight into the type of content that is needed and shall guide the contractor's update.
3.4In all sections, provide a completeand detailed description of the analysis and test and hardware changes that resulted in the final delivered design hardware.
4Submittal Instructions:Use DD Form 1696 to prepare a Specification Change Notice as the cover page(s) to the HDM Update change pages or, if the update is simple and the government program office responsible for the HDM agrees, use AF Form 3925 to prepare an Engineering Order as the cover page(s) to the HDM Update change pages. Follow the Air Force process for specification changes IAW EIA-649 for specification changes (using the DD Form 1696) or for configuration data changes (AF Form 3925).
Schema v3.0Community-maintained · Verify against ASSIST 