Lecture 2.1b: DoD Acquisition
Process (SEF Ch 2)
Dr. John MacCarthy
UMBC CMSC 615
Fall, 2006
1
Chapter 2: Systems Engineering Management
in DoD Acquisition [1]

Chapter 2:









2.1 Introduction
2.2 Recent Changes
2.3 Acquisition Life Cycle
2.4 SE in Acquisition
2.5 Summary Points
S2-A Technology Readiness Levels
S2-B Evolutionary Acquisition Considerations
NEW DOD 5000 Process:
User Needs &
Technology Opportunities

Process entry at Milestones A, B, or C

Entrance criteria met before entering phase

Evolutionary Acquisition or Single Step to Full
Capability
(Program
A
Concept
Refinement
B Initiation)
Technology
Development
C
System Development
& Demonstration
IOC
Production &
Deployment
Concept
Decision
Design
Readiness
Review
Pre-Systems Acquisition
Systems Acquisition
LRIP/IOT&E
FOC
Operations &
Support
FRP
Decision
Review
Sustainment
Notes:



The current SEF Guide describes the OLD DODI 5000.2-R
Acquisition Process
We just discussed the NEW version (DODI 5000.2)
Some Major Differences:









OLD DOD 5000.R Process
Concept & Technology Development are separated by MS-A
Name of the final Phase Changed
Some new Milestones
MNSs and ORDs are replaced by ICDs and CDDs
Others
USE THE NEW ACQUISITION WALL CHART
As such, although many of the specifics of Chapter 2 are
dated, the general approach described for iterative
application of the SEP process to the DoD Acquisition
Phases is still valid.
Chapter 2 Conclusions are still valid.
2
Chapter 2: Systems Engineering Management
in DoD Acquisition [2]

Overview of OLD DoD 5000.R
Concept Subphase

Overview of OLD DoD 5000.R
Technology Development Subphase
Note: This model is no longer valid. See NEW Acquisition wall chart for
NEW Concept Development and Technology Development Phases.
3
Chapter 2: Systems Engineering Management
in DoD Acquisition [3]

Overview of SE Process in OLD SDD
Phase (System Requirements):

Overview of SE Process in OLD SDD Phase
(Design Requirements & Design):
Note: Time Scale is off. See NEW Acquisition wall chart for SDD Phase.
4
Chapter 2: Systems Engineering Management
in DoD Acquisition [4]

Overview of SE Process in OLD
Production and Deployment Phase:

Overview of SE Process in OLD
Operations & Support Phase:
Note: Time Scale is off. See NEW Acquisition wall chart for
Product & Deployment and Sustainment & Disposal Phases.
5
2.5 Summary Points



The development, acquisition, and operation of military systems is governed by a multitude
of public laws, formal DoD directives, instructions and manuals, numerous Service and
Component regulations, and many inter-service and international agreements.
The system acquisition life cycle process is a model used to guide the program
manager through the process of maturing technology based systems and readying them
for production and deployment to military users.
The acquisition process model is intended to be flexible and to accommodate systems
and technologies of varying maturities:




Systems dependent on immature technologies will take longer to develop and produce,
Systems that employ mature technologies can proceed through the process relatively quickly.
The system engineering effort is integrated into the systems acquisition process
such that the activities associated with systems engineering (development of
documentation, technical reviews, configuration management, etc.) support and
strengthen the acquisition process.
The challenge for the engineering manager is to ensure that engineering activities
are conducted at appropriate points in the process to ensure that the system has, in fact,
achieved the levels of maturity expected prior to progressing into succeeding phases.
6
S2-A Technology Readiness Levels




New DOD 5000.2 Process requires a
Technology Readiness
Assessment (TRA) prior to
Milestone B (for Major Acquisitions)
Critical Technologies need to be
identified and characterized by
Technology Readiness Level
(TRL)
Chart to right provides definition for
each level.
For Milestone B, most (all) critical
technologies should be at TRL 5/6 or
higher
7
S2-B Evolutionary Acquisition Considerations [1]

Evolutionary Acquisition is
Characterized by:



Evolving Architectures
Block Development & Incremental
Delivery (each block provides
additional or upgraded capability)
Phased, concurrent development
of Blocks/Increments

Planning Considerations:





Clear description of core system and subsystems/ components most
likely to evolve
Process for obtaining, evaluating and integrating operational feedback,
technology advancements, & emerging commercial Products
Planning for evolutionary block upgrade evaluation, requirements
validation and program initiation
Description of the management approach for evolutionary upgrades
with in block and the constraints and controls associated with
incremental delivery of capability
Risk Analysis of the developmental approach, both technical and
managerial
8
S2-B Evolutionary Acquisition Considerations [2]

SE Planning Emphasis:





Openness and Modularity of
the design of the core system
architecture (to facilitate
upgrades)
Structure of Baseline
Documentation (upgrade
flexibility)
Impact of Evolutionary
Acquisition on baseline
development and document
control
Structure of technical reviews
to best support acquisition
decision points
Risk Management monitoring
and controlling of the
programmatic and technical
complexity associated with EA.

EA Considerations and Relationships:
9