DI-NDTI-81942

Recurring Hardware Requirements Verification Documentation

The Hardware Requirements Verification Documentation is used to obtain detailed plans and procedures used to demonstrate traceability to each applicable Performance Specification and Drawing Requirement.

Approval DateAugust 27, 2013

AMSC NumberN9427

Preparing Activity—

Project Number—

OPRSH/PEOSUB/PMS404

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantNo

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Hardware Requirements Verification Documentation will be used to obtain detailed information on plans and procedures used to meet the specific requirements of the product in order to demonstrate traceability to each applicable Performance Specification and Drawing Requirement.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

Preparation Instructions

1Format.The Hardware Verification Documentation shall be in the contractor's format.

2Content.The Verification Documentation shall contain a title page specifying the following:

2.1CDRL number

2.2Contract number

2.3Contractor's name and address

2.4Date of issue

2.5Distribution statement

2.6Security classification (if applicable)

2.7Revision date (if applicable)

2.8Record of changes (if applicable)

3The Contractor's plans for conducting all recurrent testsThe documentation shall include in detail, the Contractor's plans for conducting all recurrent tests and how he plans to analyze the test results to show how the hardware items satisfy the requirements of the applicable design and performance specification(s).

4The following information for each hardware itemThe documentation shall include the following information for each hardware item:

4.1Requirements traceability matrix

4.2Details how each design and performance specification requirement will be verified.

4.3Identity of the assembly level at which verification will take place.

4.4A list of the test and inspection procedure reference(s) that will be used for verification.

5The documentation shall contain a flow diagramThe documentation shall contain a flow diagram that reflects the functional description and location of the manufacturing test program, including Highly Accelerated Stress Screening (HASS), within the prime Contractor's and suppliers' facilities. A block diagram portrayal of the functions that must be met to satisfy the design and performance specifications and specifies the order of testing to be performed and any dependencies on earlier testing. Identify which tests and inspections will comprise Pre-FAT or FAT category performed within the prime Contractor's facility.

6A list of pass-thru itemsThe documentation shall contain a list of pass-thru items that describes the inspections, tests, or criteria implemented by the prime Contractor to verify satisfactory hardware design and performance to specifications.

7The factory acceptance test (FAT) performedThe documentation shall include the factory acceptance test (FAT) performed and shall identify inspections, tests, and acceptance criteria performed within the prime Contractor's facility for each item listed.

8Government test facilitiesGovernment test facilities shall be identified and shall include a reference to the appropriate private party work agreement and the test availability plan, if applicable.

9Step-by-step testing operationsThe documentation shall include step-by-step testing operations to be performed to show how the hardware item will satisfy the requirements of the applicable design and performance specifications. All procedures shall be listed in the order in which they were performed and shall also include:

9.1Procedure description

9.2Name

9.3Number

9.4Revision

9.5Nomenclature

9.6Model

9.7Part number of the assembly level item to be tested.

10A summary of the each tests objectiveThe documentation shall include a summary of the each tests objective and shall identify:

10.1Duration.

10.2Number of Cycles.

10.3Parameters Monitored.

10.4Data analysis.

10.5A description of all the data analysis tools and techniques that will be used to interpret the data.

10.6Success/failure criteria.

10.7Retest criteria and process.

11A list of all equipment to be usedThe documentation shall include a list of all equipment to be used, including the instrumentation and recording devices, used during the test.

12The step-by-step operator instructions and approachThe step-by-step operator instructions and approach used to perform each test shall be specified.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer