Download Free The Role Of Specifications And Standards In The Department Of Defense Acquisition Process Book in PDF and EPUB Free Download. You can read online The Role Of Specifications And Standards In The Department Of Defense Acquisition Process and write the review.

The purpose of this thesis was to investigate the role of the nongovernment standards setting bodies and the Department of Defense in the standards setting process, and; current DoD initiatives to streamline the acquisition process via more efficient selection and application of standards and specifications. Discussions and analyses were conducted in the areas of private standards setting organizations, motives for developing and using standards, various types of standards, and some problems encountered regarding the use or non-use of standards. Attention was focused on Department of Defense (DoD) policies and procedures for the development and adoption of standards and specifications and methods of interacting with nongovernment standards setting organizations. Specific examples were discussed regarding specification and standardization problems in the DoD followed by review of the DoD's Streamlining Initiative. Conclusions reached were: Methods used by the DoD to develop, write, and adopt standards and specifications were undecipherable from current literature; DoD specifications and standards are applied in a haphazard manner, and; The Streamlining Initiative is a successful step in solving some of the DoD's problems with over specification.
The U.S. Air Force has experienced many acquisition program failures - cost overruns, schedule delays, system performance problems, and sustainability concerns - over program lifetimes. A key contributing factor is the lack of sufficient technical knowledge within the Air Force concerning the systems being acquired to ensure success. To examine this issue, the Assistant Secretary of the Air Force for Acquisition requested that the Air Force Studies Board of the National Research Council undertake a workshop to identify the essential elements of the technical baseline - data and information to establish, trade-off, verify, change, accept, and sustain functional capabilities, design characteristics, affordability, schedule, and quantified performance parameters at the chosen level of the system hierarchy - that would benefit from realignment under Air Force or government ownership, and the value to the Air Force of regaining ownership under its design capture process of the future. Over the course of three workshops from November 2014 through January 2015, presenters and participants identified the barriers that must be addressed for the Air Force to regain technical baseline control to include workforce, policy and process, funding, culture, contracts, and other factors and provided a terms of reference for a possible follow-on study to explore the issues and make recommendations required to implement and institutionalize the technical baseline concept. Owning the Technical Baseline for Acquisition Programs in the U.S. Air Force summarizes the presentations and discussion of the three workshops.
This research note presents a thorough analysis of Department of Defense and service-level policy requirements for human factors in the military system acquisition process. It is intended as a companion document to ARI Technical Report No. 476, and as such provides detailed indoctrination into both the system development process and human factors R & D. It will be particularly useful to those who require a greater understanding of this process. Beginning with an explanation of each system development phase, human factors R & D requirements are then integrated into the system development framework. This is accomplished through direct referral to Department of Defense Directives, Specifications, and Standards. Recognizing that differences occur in Army, Navy, and Air Force implementation of human factors R & D, formal service documentation is presented for human factors in each phase of system development. These documents include service regulations and instructions. Formal service documentation provides only that human factors requirements be implemented, while not setting forth a particular implementation plan. Informal service documentation is presented to illustrate the processes by which human factors is implemented in system development programs initiated by each service. (Author).