|
TECHNICAL MATURITY POINTS
|
|
DoD Acquisition Milestone/Decision Point
&
Technical Review/Audit
|
Objective
|
Technical Maturity Point
|
Additional Information
|
|
Materiel Development Decision (MDD)
|
Decision to assess potential materiel solutions and appropriate phase for entry into acquisition life cycle.
|
Capability gap met by acquiring a materiel solution.
|
Technically feasible solutions have the potential to effectively address a validated capability need. Technical risks understood.
|
|
Alternative Systems Review (ASR)
|
Recommendation that the preferred materiel solution can affordably meet user needs with acceptable risk.
|
System parameters defined; balanced with cost, schedule, and risk.
|
Initial system performance established and plan for further analyses supports Milestone A criteria.
|
|
Milestone A
|
Decision to invest in technology maturation and preliminary design.
|
Affordable solution found for identified need with acceptable technology risk, scope, and complexity.
|
Affordability targets identified and technology development plans, time, funding, and other resources match customer needs. Prototyping and end-item development strategy for Technology Development (TD) phase focused on key technical risk areas.
|
|
System Requirements Review (SRR)
|
Recommendation to proceed into development with acceptable risk.
|
Level of understanding of top-level system requirements is adequate to support further requirements analysis and design activities.
|
Government and contractor mutually understand system requirements including
(1) the preferred materiel solution (including its support concept) from the Materiel Solution Analysis (MSA) phase,
(2) available technologies resulting from the prototyping efforts, and
(3) maturity of interdependent systems.
|
|
System Functional Review (SFR)
|
Recommendation that functional baseline fully satisfies performance requirements and to begin preliminary design with acceptable risk.
|
Functional baseline established and under formal configuration control. System’s functions decomposed and defined to lower levels in order to start preliminary design.
|
Functional requirements and verification methods support achievement of performance requirements. Acceptable technical risk of achieving allocated baseline.
|
|
Preliminary Design Review (PDR)
|
Recommendation that allocated baseline fully satisfies user requirements and developer ready to begin detailed design with acceptable risk.
|
Allocated baseline established such that design provides sufficient confidence to support 2366b certification.
|
Preliminary design and basic system architecture support capability need and affordability target achievement.
|
|
Pre-Engineering and Manufacturing Development (EMD) Review
|
Determination that program plans are affordable and executable and that the program is ready to proceed to EMD phase source selection.
|
Systems engineering trades completed and have informed program requirements. Competitive prototyping and the development of the preliminary design have influenced risk management plans and should cost initiatives.
|
The Request for Proposal (RFP) reflects the program’s plans articulated in the draft Acquisition Strategy and other draft, key planning documents such as the Systems Engineering Plan (SEP), Program Protection Plan (PPP), Test and Evaluation Master Plan (TEMP), and Life-Cycle Sustainment Plan (LCSP).
|
|
Milestone B
|
Decision to invest in product development, integration, and verification as well as manufacturing process development.
|
Critical technologies assessed able to meet required performance and are ready for further development. Resources and requirements match.
|
Maturity, integration, and producibility of the preliminary design (including critical technologies) and availability of key resources (time, funding, other) match customer needs. Should cost goals defined.
|
|
Critical Design Review (CDR)
|
Recommendation to start fabricating, integrating, and testing test articles with acceptable risk.
|
Product design is stable. Initial product baseline established.
|
Design is stable and performs as expected. Initial product baseline established by the system detailed design documentation confirms affordability/should-cost goals. Government control of Class I changes as appropriate.
|
|
System Verification Review (SVR)
|
Recommendation that the system as tested has been verified (i.e., product baseline is compliant with the functional baseline) and is ready for validation (operational assessment) with acceptable risk.
|
System design verified to conform to functional baseline.
|
Actual system (which represents the production configuration) has been verified through required analysis, demonstration, examination, and/or testing. Synonymous with system-level Functional Configuration Audit (FCA).
|
|
Production Readiness Review (PRR)
|
Recommendation that production processes are mature enough to begin limited production with acceptable risk.
|
Design and manufacturing are ready to begin production.
|
Production engineering problems resolved and ready to enter production phase.
|
|
Milestone C
|
Decision to produce production-representative units for operational test and evaluation (OT&E).
|
Manufacturing processes are mature enough to support Low-Rate Initial Production (LRIP) and generate production-representative articles for OT&E.
|
Production readiness meets cost, schedule, and quality targets. Begin initial deployment as appropriate.
|
|
Physical Configuration Audit (PCA)
|
Recommendation to start full-rate production and/or full deployment with acceptable risk.
|
Final product baseline established. Verifies the design and manufacturing documentation matches the item to be fielded, following update of the product baseline to account for resolved OT&E issues.
|
Confirmation that the system to be fielded matches the product baseline. Product configuration finalized and system meets users’ needs. Conducted after OT&E issues are resolved.
|
|
Full-Rate Production Decision Review (FRP DR) or Full Deployment Decision Review (FDDR)
|
Decision to begin full-rate production and/or decision to begin full deployment.
|
Manufacturing processes are mature and support full-rate production and/or capability demonstrated in operational environment supporting full deployment (i.e., system validated through OT&E).
|
Delivers fully funded quantity of systems and supporting materiel and services for the program or increment to the users.
|
DAG Tutorial 
