MIL-STD-962D
b. Do not develop standards that tell a contractor how to manage a program. It is not the policy of the DoD to create standard management approaches across all programs and all contractors. Contractors must be allowed the flexibility to manage programs in innovative ways that can improve quality, reduce costs, and introduce the latest technological advances. If a common management approach is likely to have applications across industry in meeting both commercial and defense needs, a non-Government standard should be developed. If the DoD
has a need to know how a contractor proposes to manage certain program elements, a non- contractual handbook should be used to provide guidance to DoD personnel on how to collect this information during the solicitation.
c. DoD interface standards should be developed to specify the physical, functional, or military operational environment interface characteristics of systems, subsystems, equipment, assemblies, components, items, or parts to permit interchangeability, interconnection, interoperability, compatibility, or communications. Non-Government standards should be used to the extent possible to specify interface requirements. DoD interface standards should only be developed to specify military-unique interface requirements. DoD interface standards may be
cited as solicitation requirements without need for a waiver by the Milestone Decision Authority.
d. DoD standard practices should be developed when it is necessary to specify procedures on how to conduct non-manufacturing functions. Standard practices should only be developed for functions that, at least some of the time, are obtained via contract from commercial firms. Procedures for functions performed only by DoD personnel should be covered by such documents as regulations, directives, instructions, technical manuals, or
standard operating procedures. DoD standard practices may be cited as solicitation requirements without need for a waiver by the Milestone Decision Authority.
e. DoD design criteria standards should be developed to specify military-unique design or functional criteria that must be adhered to in the development of systems, subsystems, equipment, assemblies, components, items, or parts. These design criteria are not primarily related to requirements that affect interchangeability, interoperability, interconnection, compatibility, or communications. Adherence to these design criteria standards, however, will affect the manufacturing of a product. Some examples would include military-unique design selection, nuclear blast protection, safety requirements, and human factors requirements. A DoD design criteria standard requires the Milestone Decision Authority's waiver to be cited as a solicitation requirement.
f. Non-Government standards can usually be used to satisfy DoD requirements for test methods. A DoD test method standard should only be developed if it reflects a military-unique requirement. A DoD test method standard requires the Milestone Decision Authority's waiver to be cited as a solicitation requirement.
g. The DoD discourages the development of manufacturing process standards. A DoD manufacturing process standard requires the Milestone Decision Authority's waiver to be cited as a solicitation requirement. The concept of DoD manufacturing process standards is inconsistent with both Department's emphasis on using commercial processes and reliance on performance specifications that state desired outcomes rather than "how-to's." The role for DoD
iii
For Parts Inquires call Parts Hangar, Inc (727) 493-0744
© Copyright 2015 Integrated Publishing, Inc.
A Service Disabled Veteran Owned Small Business