OSS Policy in the Military

OSS Is Allowed and Preferred

As it relates to both Federal Government and Department of Defense (DoD) acquisitions, Open Source Software(OSS) is considered “commercial computer software” products. The United States Code (
41 USC 403
), Federal Acquisition Regulations (
FAR 2.101, 12
), and Defense Federal Acquisition Supplement (
DFARS 212, 252
) all concur in the classification of OSS as a commercial software product because OSS is commonly licensed to the general public for purposes not uniquely governmental and can be modified to meet various requirements. In many cases, OSS products can also be considered “commercial off-the-shelf items” (COTS), a specific subset of commercial items (
41 USC 403
). COTS items are ready to use and require little if any customization.

To ensure efficiency and reduce the potential for waste, the Federal Government has enacted legislation (
10 USC 2377
) directing its agencies exercise a preference for commercial and nondevelopmental items (NDI) “to the maximum extent practicable”. The law’s intent to prefer COTS and NDI products is echoed in both the FAR and the DFARS. As a commercial item, an OSS product that is found to viably meet an agency's requirements must be considered alongside other commercial products being evaluated.

Department of Defense

In 2009 the DoD issued a memo providing clarification and guidance to establish the definitive interpretation of OSS as being “commercial” and therefore given preferential treatment in the acquisition process and extended that interpretation to all military services.

- 2003 Stenbit Memo1
- 2006 OTD Roadmap2
- 2009 DoD OSS Policy Memo3
- 2010 Carter Memo4

U.S. Army

- AR 25-2 p4-65

Department of the Navy (U.S. Navy & U.S. Marine Corps)

- 2007 DoN Policy Memo: Open Source Software Guidance

U.S. Air Force

To date, the United States Air Force has not defined it's own OSS policies. With the 2009 DoD OSS Memo6 in force, the Air Force will likely invoke and transmute the DoD's guidance to the Air Force.

Footnotes

1. 2003 DoD Policy Memo: Open Source Software in the Department of Defense2. Open Technology Development Roadmap3. 2009 DoD Policy Memo: Clarifying Guidance Regarding Open Source Software (OSS)4. 2010 DoD Policy Memo: Better Buying Power: Mandate for Restoring Affordability and Productivity in Defense Spending5. US Army Regulation 25-2, paragraph 4-6.h6. 2009 DoD Memo: Clarifying Guidance Regarding Open Source Software (OSS)