Department of Defense Acquisition
Yvette Rodriguez
Email: ytorres@usc.edu
Yvette Rodriguez Biography
•
Personal
• East Los Angeles Resident for 41 years
• DAU Instructor in El Segundo
•
Education
• University of Southern California - Doctoral Student, BSEE 1996
• Naval Postgraduate School - MSSE 2003
•
Teaching
• University of Southern California Teaching Assistant
• SAE 541, SAE 549, SAE 574
• Defense Acquisition University
• Systems Engineering Instructor
•
Engineering
• Port Hueneme Division Naval Surface Warfare Center
• Combat Systems Installation Engineering Lead
USN Shipboard Installations
•
May 1996, USS ASHLAND - test platform for the Ship's Self Defense
System (SSDS).
•
Performed 17 SSDS, Battle Force Tactical Trainer, AN/SPQ-9B Radar
Installations, Testing, and Sea Trials
• Landing Ship Dock Class Hulls 41 – 52
• Landing Platform Dock Class Hull 17
• Carrier Vessel Nuclear Class Hulls 68, 69, 73, 74
What is DoD Acquisition
Version 5.4 15June2010
https://ilc.dau.mil
Defense Acquisition Management System 2008
• The Materiel Development Decision precedes
entry into any phase of the acquisition framework
• Entrance criteria met before entering phases
• Evolutionary Acquisition or Single Step to Full Capability
User Needs
Technology Opportunities & Resources
A
Materiel
Solution
Analysis
B
Technology
Development
Materiel
Development
Decision
Pre-Systems Acquisition
C
Engineering & Manufacturing
Development
Integrated
System
Design
PDR
Post CDR
Assessment
FOC
Production &
Deployment
System Capability &
LRIP
Manufacturing Process
Demonstration
Post PDR
Assessment
PDR
IOC
Operations &
Support
Operations
&
Full-Rate ProdLife Cycle
Support
& Deployment
Sustainment
FRP
Decision
Review
Disposal
CDR
or
Sustainment
Systems Acquisition
• Decision points: 6
• Phases: 5
• Milestone documents: 40+
5
New in bold blue italics
Materiel Solution Analysis
OUTPUTS
INPUTS
•Draft System Requirements
• T&E Strategy
•SEP
• System Safety Analysis
• Support and Maintenance
Concepts and Technologies
• Inputs to:
-draft CDD
-AoA -TDS
-Cost/Manpower Est.
• ICD
• AoA Plan
• Exit Criteria
• Alternative Maintenance
& Logistics Concepts
ASR
ITR
Interpret User Needs,
Analyze Operational
Capabilities &
Environmental Constraints
Analyze/Assess
Concepts Versus
Defined User Needs &
Environmental Constraints
Develop Concept
Performance (& Constraints)
Definition & Verification
Objectives
Assess/Analyze
Concept & Verify
System Concept’s
Concept
Performance
Decompose Concept
Performance into
Functional Definition &
Verification Objectives
Decompose Concept
Functional Definition into
Component Concepts &
Assessment Objectives
Assess/Analyze
System Concept
Versus Functional
Capabilities
Assess/Analyze
Enabling/Critical
Components Versus
Capabilities
Develop Component Concepts,
i.e., Enabling/Critical
Technologies, Constraints,
& Cost/Risk Drivers
Technology Development
INPUTS
OUTPUTS
•ICD and Draft CDD
•Approved Materiel Solution
•Exit Criteria
•Support and Maintenance
Concepts and Technologies
•AoA •TDS
•T&E Strategy
•System Safety Analysis
•System Allocated Baseline
•PDR Report
•TEMP •SEP •PESHE •PPP •TRA
•NEPA Compliance Schedule
•Risk Assessment
•Validated Sys Support & Maint
Objectives & Requirements
•Inputs to:
-IBR -ISP -STA -CDD
-Acq Strategy
-Affordability Assessment
-Cost/Manpower Est.
SRR
Interpret User Needs.
Analyze Operational
Capabilities and
Environmental Constraints
Develop System Perf
(& Constraints) Spec and
Enabling/Critical Tech &
Prototypes Verification Plan
Demo /Validate System
& Tech Maturity Versus
Defined User Needs &
Environmental Constraints
Demo/Model
Integrated System Versus
Performance Spec
Interpret User Needs,
Refine System
Performance Specs &
Environmental Constraints
Develop System Functional
Specs & Verification Plan to
Evolve System Functional
Baseline
SFR
Develop Functional
Definitions for Enabling/
Critical Tech/Prototypes &
Associated Verification Plan
Decompose Functional
Definitions into Critical
Component Definition &
Technologies Verification Plan
Demo System &
Prototype
Functionality
Versus Plan
Demo Enabling/
Critical Technology
Components
Versus Plan
Design/Develop System Concepts,
i.e., Enabling/Critical Technologies,
Update Constraints, and
Cost/Risk Drivers
Evolve Functional
Performance Specs into
CI Functional (Design to)
Specs and CI Verification Plan
PDR
Engineering and Manufacturing Development
OUTPUTS
INPUTS
•Initial Product Baseline
•Test Reports
•TEMP
•Elements of Product Support
•Risk Assessment
•SEP •TRA • PESHE
•Life Cycle Sustainment Plan
•System Safety Analysis
•Inputs to: -CPD -STA -ISP
-Cost/Manpower Est.
•Sys Performance Spec
•Acquisition Strategy
•Exit Criteria
•APB •CDD •SEP •PPP •TEMP
•PESHE•STA
•NEPA Compliance Schedule
•Risk Assessment
•Validated Sys Support & Maint
Objectives & Requirements
•Product Support Strategy
FCA
SVR
PRR
Combined DT&E/OT&E/LFT&E
Demonstrate System to
Specified User Needs and
Environmental Constraints
Interpret User Needs,
Refine System
Performance Specs and
Environmental Constraints
Develop System
Functional Specs and
System Verification Plan
System DT&E, LFT&E & OAs,
Verify System Functionality
and Constraints Compliance
to Specs
SFR
Evolve Functional
Performance Specs into
CI Functional (Design to)
Specs and CI Verification Plan
Integrated DT&E, LFT&E &
EOAs Verify Performance
Compliance to Specs
PDR
Evolve CI Functional
Specs into Product
(Build to) Documentation
and Inspection Plan
CDR
Evolve CI Functional
Specs into Product
(Build to) Documentation
and Inspection Plan
CDR
Fabricate, Assemble,
Code to “ Build -to”
Documentation
Individual CI
Verification
DT&E
TRR
Production and Deployment
Production Qualification
Testing
OTRR AOTR
Independent IOT&E
BLRIP
Report to
Congress
Full -Up System Level LFT&E
JITC Interoperability
Certification Testing
LFTE
Report to
Congress
J-6 System Validation
INPUTS
OUTPUTS
•Test Results
•Exit Criteria
•APB •CPD •SEP •TEMP
•Product Support Package
•PESHE
•System Safety Analysis
•Production Baseline
•Test Reports
•TEMP •PESHE •SEP
•System Safety Analysis
•Input to:
- Cost/Manpower Est.
PCA
Analyze Deficiencies
To Determine Corrective
Actions
Verify and Validate
Production
Configuration
Modify Configuration
(Hardware/Software/Specs)
To Correct Deficiencies
Operations and Support
INPUTS
OUTPUTS
•Service Use Data
•User Feedback
•Failure Reports
•Discrepancy Reports
•SEP •PESHE
•System Safety Analysis
•Data for In -Service Review
•Input to CDD for next increment
•Modifications/upgrades to fielded
systems
•SEP
•System Safety Analysis
In-Service
Review
Monitor and Collect
All Service
Use Data
Implement and
Field
Analyze Data to
Determine
Root Cause
Assess Risk of
Improved System
Determine
System Risk/
Hazard Severity
Integrate and Test
Corrective Action
Develop
Corrective
Action
• Process Change – Hardware/Support
• Materiel Change
Weapon Systems Acquisition Reform Act of 2009
• WSARA Content –Three Major Categories
• Organizational/Personnel Changes
• Acquisition Policy & Process Changes
• Congressional Reporting Requirements
Sec. 102. Directors of DT&E and Systems
Engineering
• Director, Systems Engineering (SE) (Mr. Stephen Welby)
• Deputy Assistant Secretary of Defense for Systems
• Appointed by SECDEF
• Develops policies and guidance for SE
• Director, DT&E (Mr. Edward R. Greer)
• Deputy Assistant Secretary of Defense, Developmental Test and
Evaluation
• Appointed by SECDEF
• Develops policies and guidance for DT&E
• Requires joint coordination, joint DT&E/SE guidance, and joint
annual report to Congress
• Requires CAE’s with MDAPs to appropriately resource DT&E and
SE organizations, and report to the Directors within 180 days
that they have done so
Who’s Who in Acquisition
•
•
Assistant Secretary of Defense
for Research & Engineering
for Department of Defense,
Zachary J. Lemnios
Deputy Assistant Secretary of
Defense for Systems,
Mr. Stephen Welby
•
Deputy Assistant Secretary of
Defense, Developmental Test
and Evaluation, Mr. Edward R.
Greer
•
Assistant Secretary of Defense
for Acquisition , Katrina
McFarland
• Defense Acquisition University
President
Risk Management Guide
• New Risk Management
Guide
• Released August 2006
• Redefines Risk
Management Process
• Provides detailed guidance
on key activities, e.g.,
• Risk Identification
• Identification of Root
•
•
•
•
Causes
Risk Analysis
Mitigation Planning
Tracking
Planning
https://acc.dau.mil/CommunityBrowser.aspx?id=17757
Systems Engineering Plan
SYSTEMS ENGINEERING PLAN (SEP) OUTLINE
Version 1.0, 04/20/2011
Systems Engineering References
Department of Defense (DoD) Systems Engineering (SE)
References
Department of Defense Directive 5000.01, The Defense
Acquisition System
Department of Defense Instruction 5000.02, Operation of the
Defense Acquisition System
OUSD(AT&L) Directive-Type Memorandum (DTM) 09-027,
Implementation of the Weapon Systems Acquisition Reform Act
of 2009
ASA(ALT) Memorandum, Army Systems Engineering Policy
US Army RDECOM Systems Engineering Policy
Air Force Instruction 63-1201, Life Cycle Systems Engineering
Navy Systems Engineering Guide
Defense Acquisition University (DAU) Guidebook, Chapter 4
Systems Engineering
DAU Systems Engineering Fundamentals
MIL-STD-499B
Non-specific DoD SE References
INCOSE Systems Engineering Handbook, A Guide for System
Life Cycle Processes and Activities
International Organization for Standardization (ISO)/International
Electrotechnical Commission (IEC) 15288, Systems and
Software Engineering – System Life Cycle Processes
ISO/IEC 12207, Systems and Software Engineering – Software
Life Cycle Processes
ISO/IEC 26702, Application and Management of the Systems
Engineering Process
IEEE 1220-2005, IEEE Standard for Application and
Management of the Systems Engineering Process, Institute of
Electrical and Electronics Engineers, 09Sept2005
ANSI/GEIA EIA-632, Processes for Engineering a System, 01
Sept 2003