1. Reference documents. The applicable issue of any documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
2. Format and content. The Request for Deviation (RFD) shall be prepared in contractor format. The RFD content shall include the consideration to be provided if the government accepts the deviation and, where applicable, the following information:
a. a complete description of the contract requirement affected and the nature of the deviation (non-conformance).
b. number of units (and serial/lot numbers) to be delivered in this configuration.
c. any impacts to logistics support elements (such as software, manuals, spares, tools, and similar) being utilized by government personnel or to the operational use of the product.
d. information about remedial actions being taken to prevent re-occurrence of the non-conformance.
The following references may be useful in defining content: MIL-HDBK-61, Configuration Management Guidance (paragraph 4.3 and Table 4-9) and ANSI/EIA-649-1998, National Consensus Standard for Configuration Management (paragraph 5.3.4).
Replaced/Superseded by document(s)
Use, Relationships : A Request for Deviation describes a proposed departure from (a nonconformance
with) the contractually-specified configuration documentation for a specific
number of units or for a specified period of time.
A Request for Deviation enables the Government to determine the impact on
performance, operational readiness, logistics support or other affected areas.
This Data Item Description (DID) contains the format, content and preparation
instructions for the data product resulting from the work task specified in the contract.
Data Item Description submittal in Extensible Markup Language (XML) is acceptable.
An XML Document Type Definition (DTD), associated XML document template, and other
information is available from http://www.geia.org/836/