What You Need to Know About
The Federal CIO’s Memo
A Common Approach to Federal
Enterprise Architecture
Mil-OSS connects and empowers an active
community of civilian and military open source
software and hardware developers across the
United States.
This grassroots movement is a collection of
diverse patriots that work for and with the
Department of Defense and believe in adopting
open technology innovation philosophies to
effectively defend our nation.
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
1
Background Information
THE ROAD TO ‘SHARED FIRST’
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
2
The Road to ‘Shared First’
Background
FAR & DFARS Regulations
DoD & Service Policies
• OSS is considered “commercial computer software” and
therefore allowable under the United States Code, the
Federal Acquisition Regulations (FAR), and the Defense
Federal Acquisition Supplement (DFARS)
• OSS often considered “commercial off-the-shelf” (COTS)
per 41 USC 403
• OSS is preferred as commercial and
nondevelopmental items (NDI)
“to the maximum extent
practicable” under 10 USC 2377
41 USC 403; FAR 2.101, FAR 12; DFARS 212.212, DFARS 252
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
3
The Road to ‘Shared First’
• DoD Policy
– 2003 OSS in the DoD (Stenbit Memo)
Background
FAR & DFARS Regulations
DoD & Service Policies
– 2006 Open Technology Development Roadmap
– 2009 Clarifying Guidance Regarding Open Source
– 2010 Better Buying Power (Carter Memo)
• U.S. Army
– AR 25-2 p4-6
• U.S. Navy
– 2007 Open Source Software Guidance
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
4
The Road to ‘Shared First’
• Stephen VanRoekel
– Former USAIDE (Exec. Director)
Why Now?
• International IT Familiarity
The Federal CIO
• Importance of Open Standards
Abundance of OSS
Cost-Effective Solutions
– Former FCC (Mng. Director)
The Value Added
• FCC Website Relaunch on OSS Platform
Interagency Sharing
• API
Re-Deployable Solutions
Vendor-Neutral
– Former Microsoft (Sr. Director)
• Preceded by Vivek Kundra
– First CIO, had a clean slate
– Set out the 25 Points Memo
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
5
The Road to ‘Shared First’
• Over half a million projects
• Over 5,000 sites for projects
Why Now?
The Federal CIO
Abundance of OSS
Cost-Effective Solutions
The Value Added
Interagency Sharing
Re-Deployable Solutions
• Over 2,000 licenses
• Approx. 20% of all code is Open Source
• Approx. 95% of code bases contain undisclosed OSS
code
• Over 50% of code bases contain unknown or reciprocal
(or protective) licenses
Vendor-Neutral
Black Duck Software
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
6
The Road to ‘Shared First’
• Redundant problems should never be met with
redundant problem solving
Why Now?
• Utilizes the r3 Principle
The Federal CIO
– Reuse when Possible
Abundance of OSS
– Repurpose when Practical
Cost-Effective Solutions
The Value Added
– Recycle when Plausible
Interagency Sharing
Re-Deployable Solutions
Vendor-Neutral
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
7
The Road to ‘Shared First’
• Cost-Effective Development
• Highly Efficient
Why Now?
The Federal CIO
Abundance of OSS
Cost-Effective Solutions
• Increased productivity
• Increased innovation
• Increased collaboration
The Value Added
Interagency Sharing
Re-Deployable Solutions
Vendor-Neutral
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
8
The Road to ‘Shared First’
Why Now?
The Federal CIO
Abundance of OSS
Cost-Effective Solutions
The Value Added
• Without communities of interest around Defenserelated OSS projects, they too often go unknown and
unused
• Improve the project by involving other-agency input and
collaboration
• NASA found it is easier to share agency-to-agency under
OSS license than under government re-use regulations
Interagency Sharing
Re-Deployable Solutions
Vendor-Neutral
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
9
The Road to ‘Shared First’
• The military lends itself to redundant problems
Why Now?
The Federal CIO
Abundance of OSS
Cost-Effective Solutions
The Value Added
• Redundant problems should never be met with
redundant problem solving.
• Open Source enables the reuse of solutions to common
problems
• Adaptability to expand from a basic problem into a new
solution or service.
Interagency Sharing
Re-Deployable Solutions
Vendor-Neutral
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
10
The Road to ‘Shared First’
• Readable source code makes it impossible to become
locked-in with a specific vendor
Why Now?
• Future vendor competition
The Federal CIO
• Rapid deployment is a strong case in the DoD
Abundance of OSS
Cost-Effective Solutions
• IT tools for evolving mission solutions.
The Value Added
Interagency Sharing
Re-Deployable Solutions
Vendor-Neutral
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
11
Common Approach to
Federal Enterprise Architecture
ABOUT CAFEA
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
12
Shared First
~
OSS
• Common Approach to Federal EA (CAFEA)
What is it?
• Replaces the 2001 Practical Guide to Federal
Enterprise Architecture
Policy
• Released 2 MAY 2012
Progressive
Groundwork
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
13
Shared First
~
OSS
• Forward-Looking
• “Future-Ready”
What is it?
Policy
• Keenly aware of the UK’s Open-Source First Policy
Debacle
Progressive
Groundwork
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
14
Shared First
~
OSS
• Not Exactly OSS Policy, but Gets Close
• The ‘Principles’ Are In-Line with OSS
What is it?
Policy
Progressive
Groundwork
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
15
Shared First
~
OSS
• Services should be standardized within and between
agencies where possible (p14)
Excerpts
Principles Relevant to OSS
Collaborative Planning
Methodology
Shared First
• Data and information exchange should be based on
open standards (p15)
• Use well documented interfaces built on nonproprietary open platforms using standard platform
independent data protocols (such as XML) (p15)
• Open-source software solutions should be included in
alternatives analyses (p15)
• Use cloud-based application, platform, and
infrastructure hosting designs whenever possible to
promote scalability, cost-efficiency, and metering (p15)
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
16
Shared First
~
OSS
Collaborative Planning Methodology
Excerpts
Principles Relevant to OSS
Collaborative Planning
Methodology
Shared First
mil-oss.org
• “CPM is structured to embrace the principles of
leverage and reuse by assisting planners in determining
whether there are other organizations that have
previously addressed similar needs, and whether their
business model, experiences and work products can be
leveraged to expedite improvement.” (p16)
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
17
Shared First
~
OSS
Shared First
Excerpts
Principles Relevant to OSS
Collaborative Planning
Methodology
Shared First
mil-oss.org
• “In alignment with “Shared First” principle, it is at this
point that the planners consult both internal and
external service catalogs for pre-existing services that
are relevant to the current needs. In some instances, an
entire business model, policy, technology solution, or
service may be reusable . . . an important benefit in
these cost-constrained, quickly evolving times.” (p18)
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
18
Shared First
~
OSS
• Open Source advocates are not anti-competition
• Other business models can be successful and effective
Outcomes
OSS First Best Stance
Danger of OSS Only
Future Policies
mil-oss.org
• Best solutions come from open competition, putting all
solutions on equal footing is ideal for competition
• Reusing its assets before acquiring new ones is ideal for
the Federal Government
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
19
Shared First
~
OSS
• The Debacle in the UK
Outcomes
OSS First Best Stance
Danger of OSS Only
Future Policies
• Economically harms competitors with different business
models
• Hampers innovation from some private-sector
companies with proprietary business models.
• Ties the hands of Acquisition professionals
• Forces companies into a particular business model to do
business with the Federal Government.
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
20
Shared First
~
OSS
• Clearly include “Open Source” in the language
Outcomes
• Continue to promote r3
• Work with legislators to improve code reuse
OSS First Best Stance
Danger of OSS Only
Future Policies
mil-oss.org
What You Need to Know About The Common Approach to Federal Enterprise Architecture
23 MAY 2012
21
PRESENTATION INFORMATION
mil-oss.org
An Introduction to the Mil-OSS Community
19 JAN 2012
22
Contact Information
Presenter Kane McLean
Website mil-oss.org
Phone 202.455.8089
General Email [email protected]
Presenter Email [email protected]
Presentation Information
Version 1.0
Revised 23 MAY 2012
mil-oss.org
An Introduction to the Mil-OSS Community
19 JAN 2012
23