Urgent Capability Acquisition (UCA)

AAF  >  Urgent Capability Acquisition  >  P&D Milestone

P&D Milestone

How to use this site

Each page in this pathway presents a wealth of curated knowledge from acquisition policies, guides, templates, training, reports, websites, case studies, and other resources. It also provides a framework for functional experts and practitioners across DoD to contribute to the collective knowledge base. This site aggregates official DoD policies, guides, references, and more.

DoD and Service policy is indicated by a BLUE vertical line.

Directly quoted material is preceeded with a link to the Reference Source.

 

 

Entry into Production and Deployment (P&D)

Reference Source: DoDI 5000.81 Section 4.4.a&b

 

Entry into P&D is approved by the MDA.

 

At the P&D milestone review:

 

The PM will summarize the results of development activities, pre-deployment performance, and the program assessment to date. The PM will present plans to transport, deploy, and sustain the capability; to conduct post-deployment assessments; and to train maintenance and operating personnel, and provide this information to the MDA for approval.

 

The MDA, in consultation with the supporting developmental and operational and/or live fire test organization, and with the concurrence of DOT&E for programs under DOT&E oversight, will determine:

 

  • Whether the capability has been adequately reviewed, performs satisfactorily, is supportable, and is ready for production and deployment.

 

  • When assessments of fielded capabilities are required.

 

The MDA decides whether to produce and, in coordination with the requester/user, field the capability, approves the updated acquisition strategy, which will include the sustainment plan, and program baseline, and documents the production decision in an ADM.

Documentation Requirements

Reference Source: DoDI 5000.81

Adapted from policy for Rapid Deployment Training, March 2020

 

While these requirements are specific to programs responding to urgent operational needs, they are additive to the requirements identified in Tables 2 and 6 DoDI 5000.02 (see https://www.dau.edu/mdid/Pages/Default.aspx).

Statutory Requirements

Reference Source: DoDI 5000.81 Table 1

Adapted from policy for Rapid Deployment Training, March 2020

Assessment Approach: 10 U.S.C. §2366 and §2399

 

For programs under DOT&E oversight, operational and live fire test plans will be submitted to DOT&E for approval at the Development Milestone; post-deployment assessment plans will be submitted to DOT&E for approval at the Production and Deployment Milestone. DOT&E will ensure that testing is rigorous enough to rapidly evaluate critical operational issues. Test Plans submitted for DOT&E approval are required to be delivered 60 days before the start of testing.

 

Programs not under DOT&E oversight are approved at the Service level; the program may require a rapid and focused operational assessment and live fire testing (if applicable) prior to deploying an urgent need solution. The Acquisition Approach will identify any requirements to evaluate health, safety, operational effectiveness, suitability, environmental factors, supportability and survivability.

 

Course of Action Analysis: Subtitle III of Title 40, U.S.C.

 

Approved by the MDA.

 

For JUONs, JEONs, critical warfighter issues identified by the Warfighter SIG, and SecDef or DepSecDef RAA determinations, a copy is due to the Executive Director, JRAC, within 3 business days of MDA approval.

 

RAA Recommendation: MDA approves the decision to request RAA at the Development Milestone

Regulatory Requirements

Reference Source: DoDI 5000.81 Table 1

Adapted from policy for Rapid Deployment Training, March 2020

Disposition Authority’s Report to the DoD Component Head: Para. 4.5.e. of this issuance

 

Based on the disposition official’s recommendation in the Disposition Analysis, the Component Head will determine and document the disposition of the initiative and process it in accordance with applicable Component and requirements authority procedures.

Milestone Document Identification (MDID) Tool

The Milestone Document Identification (MDID) tool can also help to assess which acquisition information and reporting requirements are applicable to the acquisition.  Launch the tool at Milestone Document Identification Tool (MDID) (dau.edu), choose the program type, phase/event, and regulatory/statutory  source of information.  Results can be exported to Excel for the contract file or briefings.

This graphic is a screenshot of the MDID tool.  The banner reads:  Milestone Document Identification (MDID), The DoD Acquisition Information and Reporting Requirements Tool.  The screenshot shows the boxes for drop-down menus for MDID Tables, Related Resources, Find by keyword or phrase, Find, Notes, Print Results, and Export to Excel.  The tool allows for filtering by program type, such as ACAT II (Major Systems), Urgent Capability Acquisition Event such as Development Milestone, Production Milestone,  Other – an event other than the events listed above, and all events; and source type, including statutory, regulatory, and all sources.  In this screenshot, the tool is based on filters for all events and all sources.  The result for statutory is Assessment approach (for development and production), course of action analysis (for development), and Rapid Acquisition Authority (RAA) Recommendation (for other).  The result for regulatory is Disposition Authority’s Report to the Component Head (for Other).

What's Changed?

New/revised text from DoDI 5000.02, Enclosure 13, January 2015, is highlighted in red; deletions are shown as strikethrough text.

 

Entry into P&D is approved by the MDA

PM:

  • Summarizes results of development activities, pre-deployment performance, and the program assessment
  • Presents plan to transport, deploy, and sustain the capability, and to conduct post-deployment assessments, and to train maintenance and operating personnel

MDA, in consultation with the supporting operational test organization DT and OT and/or live fire test organization, with concurrence of DOT&E for programs under DOT&E oversight, determines:

 

  • Whether the capability has been adequately reviewed, performs satisfactorily, is supportable, and is ready for production and deployment.
  • When assessments of fielded capabilities are required.
  • Whether to produce and, in coordination with the requester/user, field the system capability, and
  • Approves the updated acquisition strategy (which will include the sustainment plan and program baseline)
  • Documents the production decision in an ADM