Defense Technical Documents in ASSIST

Identify the specification or standard exactly as invoked by the purchase order, drawing or contract clause. Include revision, amendment and date where specified. A partial identifier can lead to a different document family. Record any contractual precedence provision before resolving differences between the technical reference and other parts of the supply package.

ASSIST and Quick Search provide document identification and status information, with available document files and related records. Review notices and supersession information as well as the main text. A canceled or superseded document may still appear in an existing contract; its status requires a contractual decision rather than an automatic substitution by the supplier.

A product specification, test method, handbook and administrative reference serve different functions. Read the document’s scope and applicability clauses before extracting requirements. NCQM practice consideration: map each invoked requirement to the supplied item, relevant operation and required evidence. This prevents an extensive reference list from becoming an unexplained collection of presumed obligations.

Some documents or supporting data may have access or distribution restrictions. Use the authorized access route and respect the stated conditions. Availability of a public document record does not establish unrestricted access to every associated technical file. Maintain the authorized copy and document source within the organization’s controlled technical information system.

NCQM practice consideration: retain a dated reference list covering invoked documents, amendments and approved deviations. When an engineering change is proposed, review the impact on drawings, processes, qualification and inspection. A supplier should be able to show which baseline governed a particular delivery even after the public database displays a newer document revision.

ASSIST access is not supplier approval, product qualification or a contract award. Where a specification requires qualification, examine the applicable Qualified Products Database and the qualifying activity’s requirements separately. A technical document and a qualification listing answer different questions and should appear as separate evidence in the procurement review.