DODD 5000.1 AND 5000.2-R
INFORMATION POLICY
VERSUS IMPLEMENTATION
for the
DOD CALS IDE PROJECT
January 2000
Submitted by
ManTech Advanced Systems International, Inc.
West Virginia Technology Applications Operations Center
1000 Technology Drive, Suite 3310
Fairmont, West Virginia 26554
In support of
Contract DASW01-97-D-0006
Non-CDRL

1.0 INTRODUCTION
1.1 Purpose
1.2 Task Charter and Objectives
1.3 Reference
2.0 DISCUSSION
2.1 Department of Defense Policy Versus Implementation - Which Comes First?
2.2 Policy and Implementation - How Are Pilot Projects Initiated?
2.3 Department of Defense Directive and Regulation 5000 Series - Separation of Policy and Implementation
3.0 CONCLUSIONS
4.0 RECOMMENDATIONS
APPENDIX A: ACRONYMS AND ABBREVIATIONS
In order to better understand and access the relationship between Department of Defense (DoD) policy and implementation, it is important to first look at the intent as expressed in public law. This is found in the National Defense Authorization Act for Fiscal Year 2000, Report of the Committee on Armed Services House of Representatives on H.R. 1401, May 24, 1999.
It is equally important to examine DoD Directives, Guidance and Policy, Regulations, and Instructions that provide department guidance as it relates to a disciplined management approach for acquiring systems and materials to satisfy valid department needs. It is also necessary to be aware of and acknowledge current staffing arrangements within the department that facilitate and support the implementation of current department information technology policy.
1.1 Purpose
This paper presents ManTech's findings regarding information technology policy and implementation within the DoD.
1.2 Task Charter and Objectives
The objectives were as follows:
· Determine which comes first - DoD policy versus implementation.
· Discuss the relationship between policy and implementation and how pilot projects are initiated.
· Review the Department of Defense Directive (DoDD) and Regulation 5000 series for information regarding policy and implementation.
· Determine if pilot projects are classified as policy or implementation.
1.3 Reference
Research efforts included the study and analysis of:
· Public Law, the National Defense Authorization Act for Fiscal Year 2000, Report of the Committee on Armed Services House of Representatives on H.R. 1401, May 24, 1999.
· DoDD 5000.1 and DoD Regulation 5000.2-R.
· Guidance and Policy for the Department of Defense and Intelligence Community Enterprise Network (Draft).
· DoD Chief Information Officer (CIO) Guidance and Policy Memorandum No. 1-8330-052899, Information Interoperability.
· Defense Logistics Agency, Joint Electronic Commerce Program Office, Adoption of Commercial Electronic Data Interchange (EDI) for DoD Logistics Business Transactions, June 10, 1999.
· Public Law 104-106, "Subdivision E of the Clinger-Cohen Act of 1996," February 10, 1996 (formerly the Information Technology Management Reform Act of 1996).
· Secretary of Defense Memorandum, "Implementation of Subdivision E of the Clinger-Cohen Act of 1996 (Public Law 104-106)," June 2, 1997.
· DRAFT No 2(3), Handbook/Guide for Information Policy includes Information Visions, Information Policies, Information Goals and Objectives, and Information Strategic Activities. This handbook/guide was written by Jarl S. Magnusson, Director Information Policy Management, January 1999, Swedish Defense (Materiel Administration).
![]()
The survey was conducted by reviewing all the above documents, attending related presentations and lectures, and conducting interviews.