06.01.2015 Views

Defense Acquisition University

Defense Acquisition University

Defense Acquisition University

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Defense</strong> <strong>Acquisition</strong> <strong>University</strong><br />

A premier corporate university serving DoD <strong>Acquisition</strong>, Technology, and Logistics<br />

Streamlining <strong>Defense</strong> <strong>Acquisition</strong><br />

Management: What’s New<br />

Presented by:<br />

Debbie Schumann, DAU South<br />

Professor of<br />

<strong>Acquisition</strong> Management<br />

October 24, 2003


Agenda<br />

DoD Leadership Direction<br />

<strong>Defense</strong> <strong>Acquisition</strong> Framework<br />

Requirements Generation Process<br />

PPBE Updates<br />

Summary<br />

CDSC-PM , 14 May 03, New Policy - 2


DOD Leadership’s Intent<br />

For DoD 5000 Revision<br />

“….create an acquisition policy environment<br />

that fosters efficiency, flexibility, creativity,<br />

and innovation.”<br />

Revised Policy Objectives<br />

• Streamline Mandatory Procedures<br />

DEPSECDEF Wolfowitz, 30 Oct 2002<br />

• Empower PM’s to use the system vice being hampered<br />

by over-regulation<br />

• Emphasize Evolutionary <strong>Acquisition</strong> Strategies<br />

• Focus on Outcomes vice Processes<br />

• Integrate <strong>Acquisition</strong> and Requirements Processes<br />

CDSC-PM , 14 May 03, New Policy - 3


DoD Decision Support Systems<br />

Planning,<br />

Planning,<br />

Programming, &<br />

Budgeting, &<br />

Execution<br />

System<br />

(PPBE)<br />

Joint<br />

Capabilities<br />

Integration &<br />

Development<br />

System<br />

(JCIDS)<br />

Requirements<br />

Generation<br />

System<br />

(RGS)<br />

<strong>Acquisition</strong><br />

Management<br />

System<br />

(AMS)<br />

New<br />

DoDD 5000.1<br />

DoDI 5000.2<br />

CDSC-PM , 14 May 03, New Policy - 4


New Policy Documents<br />

• DoD Directive 5000.1<br />

• DoD Instruction 5000.2<br />

• Interim Guidebook<br />

•CJCSI 3170 and 3170C<br />

CDSC-PM , 14 May 03, New Policy - 5


OLD<br />

April 2002<br />

DoD 5000 Series<br />

New <strong>Acquisition</strong> Policies<br />

NEW<br />

May 2003<br />

5<br />

0<br />

0<br />

0<br />

.<br />

1<br />

5<br />

0<br />

0<br />

0<br />

.<br />

2<br />

5<br />

0<br />

0<br />

0<br />

.<br />

2R<br />

• Guiding Principles<br />

• Emphasis on Innovation<br />

• Focus on Outcomes<br />

5<br />

0<br />

0<br />

0<br />

.<br />

1<br />

5<br />

0<br />

0<br />

0<br />

.<br />

2<br />

Mandatory<br />

44 pages<br />

Mandatory<br />

251 Pages<br />

• Discretionary<br />

-Best Practices<br />

-Lessons Learned<br />

-Expectations<br />

<strong>Defense</strong><br />

<strong>Acquisition</strong><br />

Guidebook<br />

Discretionary<br />

(formerly 5000.2-R)<br />

CDSC-PM , 14 May 03, New Policy - 6


DoD Directive 5000.1<br />

The <strong>Defense</strong> <strong>Acquisition</strong> System<br />

DoDD 5000.1, chg1, 4 Jan 01<br />

• Five major categories containing<br />

14 definitive policy statements:<br />

− Achieving Interoperability<br />

− Rapid & Effective Transition from<br />

S&T to Products<br />

− Rapid & Effective Transition from<br />

<strong>Acquisition</strong> to Production<br />

− Integrated & Effective Operational<br />

Support<br />

− Effective Management<br />

• 8 pages (with 3 enclosures)<br />

Most policy statements from old<br />

DoDD 5000.1 are summarized and<br />

included in the new DoDD 5000.1.<br />

Policy was added from old DoDI<br />

5000.2 and DoD 5000.2-R<br />

DoDD 5000.1 May 03<br />

• Five major categories and 29 short,<br />

clear and concise policy statements:<br />

- Flexibility<br />

- Responsiveness<br />

- Innovation<br />

- Discipline<br />

- Streamlined & Effective Management<br />

• 8 pages (with 1 enclosure)<br />

CDSC-PM , 14 May 03, New Policy - 7


From old DoDD 5000.1<br />

− Competition<br />

− Cost & Affordability<br />

− Independent Operational Test<br />

Agency<br />

− Integrated Test & Evaluation<br />

− Interoperability<br />

− Performance-Based <strong>Acquisition</strong><br />

− Professional Workforce<br />

− Program Stability<br />

− Research & Technology Protection<br />

− Small Business<br />

− Streamlined Organizations<br />

− Technology Development &<br />

Transition<br />

− Total Systems Approach<br />

From old DoDI 5000.2 & DoD 5000.2-R<br />

− Information Assurance<br />

− Information Superiority<br />

− Knowledge-Based <strong>Acquisition</strong><br />

− Products, Services & Technologies<br />

DoD Directive 5000.1<br />

The <strong>Defense</strong> <strong>Acquisition</strong> System<br />

29 Major Policy Statements<br />

From old DoDI 5000.2<br />

− Collaboration<br />

− Cost Realism<br />

− Cost Sharing<br />

− International Agreements<br />

− Legal Compliance<br />

− SW Intensive Programs<br />

From DoD 5000.2-R<br />

−Intelligence Support<br />

−Performance-Based Logistics<br />

−Program Information<br />

−Safety<br />

−Systems Engineering<br />

NEW<br />

Financial Mgt Enterprise<br />

Architecture (FMEA)<br />

http://www.dod.mil/comptroller/bmmp/p<br />

ages/arch_home.html<br />

CDSC-PM , 14 May 03, New Policy - 8


Business Enterprise Architecture<br />

(BEA) Formerly FMEA<br />

<br />

<br />

<br />

<br />

<br />

High level Financial Blue Print to guide DoD<br />

Transformation<br />

Describes the Structural composition of DoD<br />

Business Operations<br />

Integrated Family of Products describing<br />

transformed DoD Business Operations<br />

Combining 2,100 DoD Financial Systems<br />

Reference: Bob Stump National <strong>Defense</strong><br />

Authorization Act for FY 2003, Sec. 1004<br />

CDSC-PM , 14 May 03, New Policy - 9


The <strong>Defense</strong> <strong>Acquisition</strong> Management<br />

Framework<br />

User Needs &<br />

Technology Opportunities<br />

DoDI 5000.2, Oct 2000<br />

A<br />

Concept & Technology<br />

Development<br />

Decision<br />

Review<br />

Pre-Systems <strong>Acquisition</strong><br />

B<br />

(Program<br />

Initiation)<br />

System Development<br />

& Demonstration<br />

Interim<br />

Progress<br />

Review<br />

C<br />

Systems <strong>Acquisition</strong><br />

Production &<br />

Deployment<br />

LRIP/OT&E<br />

FRP<br />

Decision<br />

Review<br />

Operations &<br />

Support<br />

Sustainment<br />

Concept<br />

Refinement<br />

Concept<br />

Decision<br />

A<br />

User Needs &<br />

Technology Opportunities<br />

Technology<br />

Development<br />

Pre-Systems <strong>Acquisition</strong><br />

B<br />

(Program<br />

Initiation)<br />

System Development<br />

& Demonstration<br />

Design<br />

Readiness<br />

Review<br />

Normally 5 years<br />

C<br />

Systems <strong>Acquisition</strong><br />

Production &<br />

Deployment<br />

LRIP/IOT&E<br />

DoDI 5000.2, May 2003<br />

FRP<br />

Decision<br />

Review<br />

Operations &<br />

Support<br />

Sustainment<br />

CDSC-PM , 14 May 03, New Policy - 10


Evolutionary <strong>Acquisition</strong><br />

Increment 2<br />

Increment 3<br />

OR<br />

Single Step to<br />

Full Capability <br />

Key Considerations<br />

• Urgency of Requirement<br />

• Maturity of Key Technologies<br />

• Interoperability, Supportability, and Affordability of<br />

Alternative <strong>Acquisition</strong> Approaches<br />

• Cost/Benefit of Evolutionary vs. Single Step Approach<br />

CDSC-PM , 14 May 03, New Policy - 11


DoD Instruction 5000.2<br />

Operation of the <strong>Defense</strong> <strong>Acquisition</strong> System<br />

Evolutionary <strong>Acquisition</strong><br />

• Two development processes to implement Evolutionary<br />

<strong>Acquisition</strong> Strategy<br />

Incremental<br />

Development: End-state is known, and<br />

requirement will be met over time in several increments<br />

SpiralSpiral Development: Desired capability is identified, but<br />

end-state requirements are not known at Program<br />

Initiation. Future increments dependent upon technology<br />

maturation and user feedback from initial increments<br />

• Evolutionary acquisition strategies shall be preferred<br />

approach to satisfying operational needs.<br />

• Spiral development shall be the preferred process.<br />

CDSC-PM , 14 May 03, New Policy - 12


A<br />

B<br />

Evolutionary <strong>Acquisition</strong><br />

CR TD SDD PD OS<br />

C<br />

B<br />

C<br />

Increment 2<br />

B<br />

C<br />

Increment 3<br />

Key Enablers<br />

• User’s Time-Phased Requirements<br />

• A Modular Open Systems Approach to<br />

facilitate Technology Insertion<br />

• Evolutionary Sustainment Strategies<br />

• T&E Consistent with Evolutionary Approach<br />

• Full Funding of Increments<br />

CDSC-PM , 14 May 03, New Policy - 13


Each Increment Must Have…<br />

B<br />

C<br />

Increment 2<br />

B<br />

C<br />

Increment 3<br />

• Milestone Entry Point<br />

• Approved Operational Requirements (KPP: Interoperability)<br />

• Technical, Cost and Schedule Goals (APB)<br />

• Operational and Live Fire Testing (If Required)<br />

• Compliance with <strong>Acquisition</strong> Oversight Requirements<br />

• <strong>Acquisition</strong> Strategy reflecting consideration of Logistics Planning;<br />

Manpower, Personnel & Training; Environmental & Security Factors;<br />

Protection of Critical Program Information; & Spectrum Management<br />

• Other information tailored to the conditions of the program<br />

Each Increment is Managed as a Unique <strong>Acquisition</strong><br />

CDSC-PM , 14 May 03, New Policy - 14


DoD Instruction 5000.2<br />

Operation of the <strong>Defense</strong> <strong>Acquisition</strong> System<br />

New/Revised from previous 5000.2:<br />

• MS B required for each increment of EA strategy<br />

• New: “Technology Dev Strategy” required for<br />

each increment of EA strategy<br />

• Revision of EA and spiral development (SD)<br />

definitions (“blocks” to “increments”)<br />

• SDD IPR now Design Readiness Review (DRR)<br />

• RFP can be released prior to AS approval – MDA<br />

option<br />

• Establishes ITAB (formerly MAISRC)<br />

CDSC-PM , 14 May 03, New Policy - 15


DoD Instruction 5000.2<br />

Operation of the <strong>Defense</strong> <strong>Acquisition</strong> System<br />

• New/Revised material (continued):<br />

- Defines “special interest” for ACATs<br />

- Requires SAE to certify readiness for operational<br />

testing (vice Developing Agency) for programs on<br />

the OSD T&E Oversight List<br />

- New procedures for acquisition of services (En. 8)<br />

- New report: Software Resources Data Report<br />

- Adds DOTMLPF* terminology (Joint Vision 2020)<br />

*DOTMLPF = Doctrine, Organization, Training, Materiel, Leadership, Personnel, and Facilities<br />

CDSC-PM , 14 May 03, New Policy - 16


The <strong>Defense</strong> <strong>Acquisition</strong> Management<br />

Framework<br />

Summary<br />

Concept<br />

Refinement<br />

Concept<br />

Decision<br />

User Needs &<br />

Technology Opportunities<br />

A<br />

Technology<br />

Development<br />

(Program<br />

Initiation)<br />

B<br />

Normally 5 yrs<br />

C<br />

System Development<br />

& Demonstration<br />

• Process entry at Milestones A, B, or C<br />

• Entrance criteria met before entering phase<br />

• Evolutionary <strong>Acquisition</strong> or Single Step to<br />

Full Capability<br />

Design<br />

Readiness<br />

Review<br />

IOC<br />

Production &<br />

Deployment<br />

LRIP/IOT&E<br />

FRP<br />

Decision<br />

Review<br />

FOC<br />

Operations &<br />

Support<br />

Pre-Systems <strong>Acquisition</strong><br />

Systems <strong>Acquisition</strong><br />

Sustainment<br />

New<br />

Fig. 1, DoDI 5000.2<br />

CDSC-PM , 14 May 03, New Policy - 17


DoD Instruction 5000.2<br />

Operation of the <strong>Defense</strong> <strong>Acquisition</strong> System<br />

• New/Revised material:<br />

- Places emphasis on Requirements and <strong>Acquisition</strong><br />

integration; requires that:<br />

• Joint Staff lead development of joint integrated<br />

architectures (three views: operational, systems<br />

and technical)<br />

• USD(AT&L) lead development of integrated<br />

capability assessments, capability roadmaps,<br />

and investment strategies<br />

- New requirements process – Joint Staff provided<br />

details in CJCSI 3170.01C & CJCSM 3170.01 in June<br />

2003.<br />

CDSC-PM , 14 May 03, New Policy - 18


Transformation to the Joint Capabilities<br />

Integration and Development System<br />

CJCSI 3170, Jun 03<br />

RGS<br />

JCIDS<br />

Integrated at<br />

Department<br />

National<br />

Military<br />

Strategy<br />

Joint<br />

Vision<br />

Systems<br />

Joint Concept of Operations<br />

Requirements<br />

Joint Concepts<br />

Integrated Architectures<br />

Joint Capabilities<br />

Bottom Up, Often<br />

Stovepiped<br />

Top Down, “Born Joint”


New Capabilities Documents<br />

• Initial Capabilities Document (ICD) replaces MNS at<br />

Milestone A<br />

Describes desired capability. Evaluates multiple materiel<br />

approaches. Recommends a materiel approach.<br />

• Capability Development Document (CDD) replaces ORD<br />

at Milestone B<br />

Describes the SDD effort and provides KPPs for the increment.<br />

Describes program to get to complete solution.<br />

• Capability Production Document (CPD) replaces ORD at<br />

Milestone C<br />

Describes the SDD effort to produce materiel solution for the<br />

increment and provides KPPs for the production increment.<br />

Details implemented in CJCSI 3170.01C & CJCSM 3170.01<br />

CDSC-PM , 14 May 03, New Policy - 20


Planning, Programming,<br />

Budgeting and Execution<br />

(PPBE)<br />

[Formerly PPBS]


PPBE Phases<br />

<br />

<br />

<br />

<br />

<br />

Planning<br />

Assess capabilities / review threat<br />

Develop guidance<br />

Programming<br />

Turn guidance into achievable, affordable packages<br />

Six-year program (Future Years <strong>Defense</strong> Program)<br />

Budgeting<br />

Test for efficient funds execution<br />

Scrub budget years<br />

Prepare defensible budget<br />

Execution Review (concurrent with program/budget review)<br />

Develop performance metrics<br />

Assess actual output against planned performance<br />

Adjust resources to achieve desired performance goals<br />

Focus: What are we getting for our money<br />

CDSC-PM , 14 May 03, New Policy - 22


Additional Information<br />

on PPBE Process<br />

OSD PA&E website (Program Review)<br />

http://www.ra.pae.osd.mil/pr/index.htm<br />

CDSC-PM , 14 May 03, New Policy - 23


<strong>Defense</strong> <strong>Acquisition</strong> Deskbook<br />

Transition to AT&L<br />

Knowledge Sharing System (AKSS)<br />

• 1996 Original Deskbook was a resource for<br />

mandatory policy, discretionary practices,<br />

optional formats and Lessons Learned.<br />

• AKSS is the next evolution of the on-line<br />

Deskbook – the source for all acquisition<br />

knowledge.<br />

• AKSS is located at http://deskbook.dau.mil<br />

CDSC-PM , 14 May 03, New Policy - 24


Other Available Resources<br />

http://dod5000.dau.mil/<br />

• Copies of the approved DOD 5000 documents<br />

• Tutorial and Frequently Asked Questions (FAQs)<br />

• OSD Video Overview of the DOD 5000 changes<br />

• New CJCSI 3170.01C and CJCSM 3170.01<br />

documents<br />

• Terminology Review<br />

• Continuous learning modules on <strong>Acquisition</strong>,<br />

JCIDS, and the PPBE at web site,<br />

http://dau.clc.mil soon<br />

CDSC-PM , 14 May 03, New Policy - 25


Summary of Significant Changes<br />

DoD Emphasis on Innovative Tailoring<br />

Streamlined Policies<br />

DOD Documents Re-issued<br />

Streamlined Clinger Cohen Act Compliance<br />

<strong>Acquisition</strong> Framework<br />

Added Concept Decision<br />

Two new Phases<br />

Changed IPR to DRR in the SDD Phase<br />

Emphasizes Evolutionary <strong>Acquisition</strong><br />

Requirements Generation Process<br />

Changed to the JCIDS Process<br />

Focuses on Joint Requirements<br />

New Requirements Documents (ICD, CDD, CPD)<br />

PPBE Process<br />

Moving to a 2-year cycle<br />

Created Business Enterprise Architecture<br />

CDSC-PM , 14 May 03, New Policy - 26

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!