Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Configuration Management Guidance (HDBK61)

Configuration Management Guidance (HDBK61)

|Views: 23|Likes:
Published by Gordon Burns
Configuration Management Handbook
Configuration Management Handbook

More info:

Published by: Gordon Burns on Nov 16, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





7 February 2001
AMSC N/A AREA CMANDISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
This handbook is for guidance only.Do not cite this document as a requirement
This Page Intentionally Blank
 Page i
1. This military handbook is approved for use by the Office of the Under Secretary of Defense (Acquisition,Technology, and Logistics), Systems Engineering Office, and is available for use by all Departments and Agencies
of the Department of Defense. This handbook is for guidance only. This handbook cannot be cited as a requirement. If it is, the contractor does not have to comply.2. -This handbook provides guidance to DoD managers assigned the responsibility for configuration managementon how to ensure the application of product and data configuration management to defense materiel items, in eachphase of their life cycle. Acquisition practices, including the manner in which CM is specified in a contract, and theprocess of monitoring contractor application are evolving as the result of two interacting transitions.3. The first transition is the change in acquisition approach initiated in the acquisition reforms introduced in June1994, which resulted in the following conceptual changes:a. A shift from the Government imposing requirements on a contractor by citing a military standard to theGovernment asking the contractor how he intends to apply his standard management practices to agiven program and evaluating those practices against industry standards.b. Limiting the focus of Government configuration control to performance requirements rather than thedetails of the design solution in most instances.c. Basing Government oversight of contractor practice on adequacy of process rather than on inspectionof product.4. The second significant transition influencing configuration management practice results from the rapid advanceof information technology. Opportunities for improvements in methodology are constantly challenging the statusquo. The predominant media for exchange of information has transitioned from a paper base to a digital one.Information technology concepts and standards for data access, data transfer, and data sharing are increasing theopportunities for Government and industry to productively integrate information from distributed sources. BothGovernment and industry are evolving infrastructures that will support information interoperability. This is leadingtoward the heretofore conceptual notion of a true virtual enterprise that will include all the configurationmanagement information necessary for the life cycle support and maintenance of equipment and software. Each partyin the enterprise, both Government activities and contractor, will be able to input and/or access product informationvia their own diversified automated information systems.5. As a consequence of these transitions, DoD standardization for Configuration Management has evolved to theuse of industry standards rather than military standards. MIL-STDs-973 and 2549 have been cancelled, effective 30September 2000. DoD has adopted ANSI/EIA-649, “National Consensus Standard for Configuration Management,”as the guiding document providing the basic principles of Configuration Management. DoD has been instrumental inthe on-going development of EIA-836, “Consensus Standard for CM Data Exchange and Interoperability” and willadopt it when it is published by the Electronics Industries Alliance as a web-based asset. This limited coordinationrevision to MIL-HDBK-61 is being issued to provide continuing up-to-date guidance for effective application of configuration management as the transition from MIL-STDs continues.5. Beneficial comments (recommendations, additions, deletions) and other pertinent data which may be of use inimproving this document should be addressed to: Mr. George Desiderio, Systems Engineering Office(OUSD(AT&L)/IO/SE), The Pentagon, Room 3D1075, Washington, DC 20301 by using the self-addressedStandardization Document Improvement Proposal (DD Form 1426) appearing at the end of this document, by letter,or by e-mail to

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->