1
The screen shot on this slide is from the IDAT&L Life Cycle Management System, the big,
complicated wall chart
chart. It shows the details of the Systems Engineering process in the
Production and Deployment phase. It also shows the input to and the outputs from the
Systems Engineering process.
If you were to compare these input and output blocks to the input and output blocks in the
EMD phase, here’s what you’d find. There’s nothing in the Production and Deployment
phase input and output blocks that hasn’t been mentioned in the EMD phase.
The truth is that all of the input and outputs on this slide have been revised or refined as
required by the acquisition program. So, since there’s nothing new in these blocks, we’ll
pass on any further discussion of them in this presentation.
What I’d like to talk about in this presentation are three technical review activities:
The Assessment of Operational Test Readiness (or AOTR);
The Operational Test Readiness Review (or OTRR);
And, the Physical Configuration Audit (or PCA).
These three activities are highlighted with red borders on this slide so that you can see
where they are relative to other activities in the Production and Deployment Systems
Engineering phase.
Before we talk about these technical reviews, let’s describe the purpose of Systems
Engineering in the Production and Deployment phase
phase.
2
A lot of Systems Engineering work has already been completed by the time a
system gets to the Production and Deployment phase. But there’s still more SE
work to do!
At this point in the acquisition process, the integrated components are merging into
a system. Along the way, test and evaluation processes probably have revealed
issues that call for improvements or redesign.
As the system matures, the testing environment should more closely approximate
the conditions under which Warfighters will actually use the system. Early
manufacturing processes may also reveal things that were not anticipated.
The Systems
S stems Engineering effort in F
Full-Rate
ll Rate Prod
Production
ction and Deplo
Deployment
ment phase
delivers the fully funded quantity of systems and the supporting materiel and
services for the program. During this effort, units attain Initial Operational Capability.
Remember, though, in this module, we’re talking about the SE and other acquisition
processes prior to the Full-Rate Production Decision Review
3
The Operational Test Readiness Review is a multi-disciplined product and process
assessment. It’s purpose is to ensure that the system can move on to the Initial
Operational Test and Evaluation (or IOT&E) and that it will have a good chance of
being successful in the IOT&E.
The OTRR should also determine if the system is effective and suitable for service.
The Full-Rate Production Decision may actually hinge on this determination.
Remember, the system has to satisfy the performance requirements in an
operational environment in order to satisfy the Capability Production Document. So,
the testing has to verify system reliability, maintainability and supportability
performance.
The OTRR is complete when the Service Acquisition Executive evaluates and
determines the system is ready for Initial Operational Test and Evaluation.
The Department of Defense has developed an OTRR Risk Assessment Checklist.
It’s attached to the block on the Interactive DA Framework where you found this
presentation.
t ti
It’s
It’ yett another
th checklist
h kli t that
th t contains
t i dozens
d
off references
f
to
t HSI!
4
The Assessment of Operational Test Readiness (or AOTR) is a process that’s used to
determine whether a program is ready to continue its progress
progress. This is done with a detailed
analysis that uses the “Defense Acquisition Program Support Methodology.” There’s a
copy of the March 2009 version attached to the Quick Links panel of this module.
According to the Foreword of this document, the Defense Acquisition Program Support
(DAPS) Methodology provides a tailorable framework for conducting Program Support
Reviews to assist program managers and DoD decision makers in preparing for milestone
decision reviews.
It even mentions HSI! In fact,
fact there
there’s
s a pretty lengthy section devoted to HSI
HSI. And you’ll
you ll
find a series of questions on various HSI issues and HSI domains. They’re included in the
document so that Program Managers know what questions to ask at each of the milestone
decision reviews. If you’re working on an acquisition program as an HSI practitioner or an
HSI domain practitioner, it would definitely be in your best interest to take a look at those
questions. It’s always nice to know the answers before the Program Manager asks the
questions!
OK,, back to the AOTR…. DoD Instruction 5000.02 states that the Deputy
p y Under Secretary
y
of Defense for Acquisition and Technology will conduct an independent Assessment of
Operational Test Readiness (AOTR) for all ACAT ID and special interest programs.
Each AOTR has to consider the risks associated with the system’s ability to meet
operational suitability and effectiveness goals.
The assessment is based on the capabilities demonstrated in Developmental Test &
Evaluations, Operational Assessments, and the criteria described in the TEMP. The
Component Acquisition Executive has to consider the results of the AOTR prior to deciding
whether the system is ready for Initial Operational Test & Evaluation.
5
The Physical Configuration Audit (or PCA) is conducted close to the Full-Rate Production
Decision The PCA examines the actual configuration of an item being produced
Decision.
produced.
It verifies that the design documentation matches the item as specified in the contract.
The PCA also confirms that the manufacturing processes, quality control system,
measurement and test equipment, and training are being properly planned, tracked, and
controlled.
A PCA is usually conducted when the government decides to control the details of the
design. If the government chooses not to exercise this kind of control, then the contractor
should conduct an internal PCA. Either way, the PCA defines the starting point for
controlling the detail design and establishing a product baseline.
The PCA is finished when the design and manufacturing documentation match the item as
specified in the contract. If the PCA wasn’t conducted before the Full-Rate Production
Decision it should be conducted as soon as production systems are available
Decision,
available.
DoD also has a Checklist for PCA Risk Assessment. It’s attached to the block on the
Interactive DA Framework where you found this presentation. Just like the OTRR
Checklist, it contains dozens of reference to HSI!
So as you can see from the AOTR, the OTRR, and the PCA, there’s plenty of things for the
S practitioner
p ac o e to
o be do
doing
g in the
e Technical
ec ca View
e o
of the
e Production
oduc o a
and
d Deployment
ep oy e p
phase.
ase
HSI
And the vast majority of that work involves checking to make sure the documents and
activities you’ve contributed to prior to this are being executed in the right way.
6