1. IT Acquisition Reform - Update
Defense Information Systems Agency
A Combat Support Agency
IT Acquisition Reform - Update
16 August 2011

2. Agenda Overview DoD Acquisition Model Acquisition Process for IT
Defense Information Systems Agency
A Combat Support Agency
Overview
DoD Acquisition Model
Acquisition Process for IT
Acquisition Reform Tenets
Acquisition Reform Phases
Acquisition Strategy
Conclusion

3. Why Reform IT Acquisition?
Using current acquisition processes and governance…..the result:
Does Not Meet User Needs
Takes Too Long To Deliver Capabilities
Costs Too Much to Acquire
Allows Duplicative Acquisition

4. The DoD Acquisition Model

5. Current acquisition documentation
IT Related Documentation for DOD 5000 Acquisitions
Acq Decision Memorandum*
Act Info Assurance Strategy*
AoA*
Benefit Analysis & Determination* #
Certification of Spectrum DD1494*
Clinger Cohen Act Compliance*
Consideration of Technology Issues* #
Cooperative Opportunities* #
Data Mgmt Strategy* #
DoD CIO Confirmation of CCA Compliance*
DoD Component Cost Estimate*
Economic Analysis*
Exit Criteria*
ICE*
Info Support Plan*
IUID Implementation Plan*
Life Cycle Signature Support Plan*
Market Research*
MDA Program Certification*
Net Centric Data Strategy*
Nunn McCurdy Assessment & Certification*
Program Protection Plan*
System Engineering Plan*
System Threat Assessment Report*
Technology Development Strategy
T&E Strategy
Acq Program Baseline*
Acq Strategy*
Affordability Assessment*
Alternate LFT&E Plan$
Capabilities Development Document
Competition Analysis* #
Core Logistics Analysis, Source of Repair Analysis* #
Corrosion Control Plan*
Cost Analysis Requirements Document*
Independent Technology Readiness Assessment (ACAT 1D)*
Industrial Base Capabilities Considerations* #
LFT&E Waiver from Full-Up System Level Testing%
Life Cycle Support Plan*#
LRIP Quantities
Manpower Estimate*
Operational Test Agency Report of Operational T&E Results*
PESHE*
Post-CDR Report
Post-PDR Report
Replaced System Sustainment Plan
Spectrum Supportability Determination*
System Threat Assessment*
Technology Readiness Assessment*
TEMP*
Beyond LRIP Report!
IT and NSS Joint Interoperability Test Certification
IOT&E completed
LFT&E Report%
Post Implementation Review
* Document is created in this phase and updated periodically throughout the life cycle
# Part of TDS or Acquisition Strategy
Red: Statutory requirement
Black: Regulatory requirement
Green: Statutory requirement for MAIS programs
Blue: Statutory and Regulatory requirement
% OSD LFT&E oversight programs only
! OSD OT&E oversight programs only
$ OSD LFT&E oversight programs with waiver from full-up, system-level testing only
Assessment & Certification of a Critical Change to Defense Committees
CCDR
Defense Acq Executive Summary
DBSMC certification
MAIS Annual Report to Congress
MAIS Quarterly Report
Notice of MAIS Cancellation or Significant Reduction in Scope
Notification of Significant Change to the Defense Committees
Program Deviation Report
Selected Acq Report
SRDR
Unit Cost Report
Other Documentation
AoA Study Guidance
AoA Study Plan
Initial Capabilities Document*
Material Solution Analysis
Technology Development
Engineering & Manufacturing Development A
Production & Deployment
Operations & Support
FRP
MDD C B C B
Capabilities Production Document
Military Equipment Valuation* #
Operational Test Plan

6. IT Acquisition Reform Imperative
Congress
Develop and Implement a new process for Acquiring IT (FY10 NDAA Section 804)
HASC Panel on Defense Acquisition Reform Finding and Recommendations (23 March 2010)
Widely documented Problems with DoD IT Acquisitions
Federal CIO
Defense Science Board
Jan 09 – Integrating COTS
Mar ‘09 – IT Acquisition
Apr ‘09 – Fix the Acq process
Jul ‘09 – Rapid Acquisition
Industry Associations
AFEI, TechAmerica,
National Academies - Achieving Effective Acq of IT in DoD 2010
Business Leads (e.g. BENS) – Aug ‘08 Joint DISA IT Review
Improve DoD IT Acquisition
25-Pt Implementation Plan to Reform Federal IT Management
“On average, it takes the Department 81 months from when an IT program is first funded to when it becomes operational…By comparison, the iPhone was developed in 24 months. That is less time that it would take us to prepare and defend a budget and receive Congressional approval for it. Steve Jobs gets an iPhone. We get a budget. It’s not an acceptable trade.
Bill Lynn, DEPSECDEF (May 2010)
DoD Senior Leadership Vision

7. A New DoD Acquisition Process for IT
Section
804
DSB – DoD Policies and Procedures for the Acquisition of Information Technology, March 2009
Modeled on successful commercial practices
Agile software Development
Multiple, rapidly executed increments or releases of capability
Releases divided into ~6 month iterations
Iterations tested and potentially deployable
Early and continual involvement of the user
Integrated testing

8. Overview of Changes being Considered
Work Groups
Oversight & Governance
Requirements
Resourcing
Oversight/
Governance
Acquisition
Portfolio & Governance
Synchronized – Integrated governance and Capability Portfolio Management
Program oriented
Incremental delivery via projects
Frequent Stakeholder IPRs
Acquisition
Acquisition Process
Contracting
T&E & Certification
Infrequent Milestones
Separate T&E and C&A
Integrated and Continuous T&E and C&A
Federated and stove-piped
Enterprise focused to Enhance Standardization and Minimize Duplication
Architecture
Architecture
From a governance perspective, our group will try to RED-TEAM whether the new Method is superior to the Current method
Capability Elements
PPBE – Program Elements
Resourcing
Single “IT” Appropriation
Funding
R&D, Procurement, O&M
Portfolio WCF Accounts
Program oriented JCIDS “IT Box”
Capability oriented - Roadmaps
Requirements
Requirements
Rationalized w/constraints

9. IT Acquisition Reform Task Force
Chair: Deputy Secretary of Defense (DSD)
Executive Lead: DCMO
Principal Members
JCS
PD USD(AT&L)
Army CMO & SAE
ASD(NII/CIO)
Navy CMO & SAE
CA&PE
Air Force CMO & SAE
USD(C)
USD(I)
DOT&E
Integration
Lead - DCMO
Portfolio and Governance - Lead CAPE
Acquisition Process - Lead NII / DISA
Metrics – Lead Navy
Working Groups
Funding - Lead OSD Comptroller
IT Task Force
The IT Task force was launched in September
It is chaired by DSD and lead by DCMO. PD AT&L and NII represent the senior leadership team
The IT task force is charged with implementing the reforms outlined in the 804 Report (New IT Acquisition Process) to Congress
There is a standing integration team led by the DCMO
Several work groups have been commissioned to address critical issues in IT acquisition reform
Each work group is operating with a defined problem statement/problem to solve and supporting charter
The work groups are time boxed; i.e., required to deliver proposed policies and legislative proposals within a defined time line
It is anticipated that work groups will be decommissioned and new work groups created to implement the reforms outlined in 804.
The Task Force is responsible for accepting the recommendations of the work groups or providing guidance if proposals are insufficient and ultimately implementing new policies tied to IT acquisition reform
The IT task force and the work groups have representation from stakeholders throughout OSD, JCS and the MILDEPS
The IT task force is looking for “pilots” programs that will run in parallel to the work groups
The pilots are intended to “test” proposed policies before they are implemented on a large scale basis
The task force is reviewing potential pilots now; it is anticipated that pilots will cover small, medium and large programs, programs at various stages of the acquisition lifecycle and programs that can use some of the “templates” envisioned by the task force
Note: Templates are a new concept proposed as part of IT acquisition reform; perspective programs would choose a template (hardware, software, service, ERP or custom development) to manage their acquisition; the template would be tailored to the unique IT acquisition.
Requirements - Lead Joint Staff / Air Force
Contracts - Lead AT&L / Army
Test, Evaluation/C&A - Lead DISA TEO
Human Capital - Lead DoD CIO
Architecture and Systems Engineering – Lead DoD CIO

10. What Does DoD’s IT Acquisition Reform Affect?
New process is applicable across the DoD IT Enterprise (including National Security Systems) in the following categories:
Networked IT Systems (e.g., command and control, business information):
User-facing applications
Computing infrastructure (e.g., common applications, operating system)
Security and information assurance for applications, systems, and networks
Computing hardware including configuration modification for network integration, etc. (e.g., servers, laptops)
Communications/networking infrastructure
Note: IT hardware requiring unique development and requisite production decisions will be acquired using traditional DoD acquisition policy (DoD 5000 processes) to ensure appropriate focus on these areas.
Weapon Platform IT Systems
Platform-hosted IT mission systems that are not considered embedded
Note: IT embedded in weapon systems will continue to be developed, acquired, and managed as part of that weapon platform and not separately acquired under the new IT acquisition process. Upgrades to embedded IT software in weapon systems may be considered for applicability to the new IT acquisition process when no hardware change is required. This will be reviewed on a case-by-case basis.
Services acquired or developed as a service-oriented architecture

11. IT Acquisition Tenets
Deliver meaningful increment of capability in 18 months or less. Larger capabilities will be delivered in a series in increments, each of which provides useful capability. Planning and execution will occur within a level of effort funding top line.
Use outcome and performance based metrics. Metrics define improvements to the capability and provide clear and coherent way to measure both process and system improvements.
Leverage enterprise services and assets (Emphasize open standards and common platforms) Emphasize the use of open standards and common platforms by use of enterprise systems, processes, infrastructure, and services (e.g., Common systems engineering, RACE, Forge.mil, NCES) to maximum extent practicable
Conduct testing and certification/accreditation “in stride”. Integrated testing and certification will occur throughout the implementation phase.

12. IT Acquisition Tenets (cont’d)
Assure agility by allowing trade-offs within dollar and time limits. Accommodate requirements trades (features, performance) reflecting user priorities, feedback, and technology advances/limitations during planning and execution.
Manage by capability-based portfolios. Portfolio construct for efficient development, fielding, and operation of like capability investments across the DoD Enterprise. Frequent in-process-reviews to replace major program oriented milestones.
Allow tailorable processes. Project execution should be tailored for the particular risks, acquisition life cycle, and oversight needs of different types of IT acquisition efforts.
Comply with enterprise and segment architectures. Assure designs are consistent with promulgated architecture policies and standards to facilitate system interoperability and integration.

13. DoD IT Acquisition Reform – Phase 1
Phase 1: Internal and external communication of flexibilities already in current acquisition policies and statutes – Mar 2011
Identify process flexibilities within current policy and statute
Begin communication activities by end of March 2011

14. DoD IT Acquisition Reform – Phase 2
Phase 2: Create a single, integrated (end-to-end) interim IT acquisition policy and implementation plan for use by Section 804 Piloting activities – Jun 2011
Mar/Apr 2011 continue to integrate WG deliverables into a single process
Initial draft of end-to-end IT acquisition policy and implementation plan – Apr 2011
Includes draft pilot project process
Refine IT acquisition policy and plans – May/Jun 2011
Non-pilot activities continue to use current DoD IT acquisition processes

15. Phase 3 Pilot Strategy Pilot Process
Purpose – Pilots will be used to evaluate the new IT acquisition process and incorporate lessons learned into proposed regulation and statutory changes
Scope – Individual pilot efforts each evaluate a subset of IT Acquisition Reform Tenets
(e.g. Portfolio Management, Funding, Requirements Process, etc.)
DoD organizations will propose both project and portfolios for pilot consideration
Pilot Process
Pilot Proposal
(Identifies value proposition for using new process)
Requesting
Organization
DCMO
Coordinator
Identifies pilot review board
membership
Pilot Review
Board
Recommends
approval/ disapproval/ changes to proposal
*co-signed by additional
Task Force membership
as required
Pilot Designation Letter
Direction to execute pilot
Delegates authorities*
Pilot Activity
Pilot execution with periodic in-process-reviews and metrics reports
Pilot Identification
Pilot Approval
Pilot Execution

16. DoD IT Acquisition Reform – Phases 3 & 4
Phase 3: Implement interim IT acquisition policy for pilot projects – Jul 2011-June 2012
Monitor pilots and incorporate lessons learned as changes to IT acquisition policy and implementation plan
Coordinate proposed legislative changes necessary for Department-wide implementation
Finalize IT acquisition policy and implementation plan – Jun 2012
Phase 4: Implement new IT acquisition policy Department-wide - Jul 2012

17. Phased Implementation Strategy1 3 4
DoD-wide Memorandum emphasizing use of flexibility within
current policy and statute
Implement integrated interim policy for approved pilots
DoD-wide integrated policy incorporating statutory changes
Mar ‘11
Jun ‘11
Jun ‘12 2
Develop integrated interim policy for approved pilots
Phases
Schedule
WG COAs
Develop
Integrate
Update
Task Force
Pilot Program
Propose
Execute
Report

18. Questions?