Urgent Capability Acquisition (UCA)

AAF  >  Urgent Capability Acquisition  >  Development Milestone

Development 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 Development

Reference Source: DoDI 5000.81 Section 4.3.a

Entry into development is approved by the MDA.

 

The PM will provide acquisition strategy and program baseline to include program requirements, schedule, activities, program funding, assessment approach, and intermediate decision points and criteria as the basis for this decision.

 

The MDA will:

 

Determine the feasibility of fielding the capability within the required timelines to include consideration of the technical maturity of the preferred solution(s). If the MDA determines that the fielding of the capability cannot be accomplished in the required timelines, then the MDA may direct partial or interim solutions that can be fielded more rapidly, or may direct that the program will be managed under a different authority.

 

Review the acquisition strategy and program baseline and determine whether the preferred solution:

      • Can be fielded within 2 years.
      • Does not require substantial development effort.
      • Is based on technologies that are proven and available.
      • Can be acquired under a fixed price contract.
      • Provides any exceptions necessary, including exceptions to the requirements of Paragraph (2)(b)1 through Paragraph (2)(b)4 (refers to the bullets above).

 

Approve initial quantities to be produced and assessed, to include required assessment and training articles.

 

Approve the tailored acquisition strategy and acquisition program baseline.  These documents will be based on available information and updated as directed by the MDA.

 

Decide if RAA, in accordance with Section 806(c) of PL 107-314, should be requested from the SecDef or DepSecDef to expedite the fielding of the capability

 

Approve the planned testing approach. A normal test and evaluation master plan (TEMP) is generally not necessary.

      • TEMPs are usually not appropriate for efforts using urgent capability acquisition procedures when there is minimal development work and minimal development work and minimal test and evaluation to execute. Some test planning is usually required, however, in collaboration with the supporting developmental or operational test organization. The MDA may require a highly-tailored and abbreviated test plan. The abbreviated test plan will describe a performance assessment approach that will include schedule, test types and environment, and assets required.
      • A TEMP is also not normally required if the urgent capability acquisition effort is under DOT&E oversight. The PM, in collaboration with the supporting operational test organization, should prepare operational and live fire test plans for DOT&E approval, however. An operational test plan for the required pre-deployment performance assessment is generally adequate.

 

Approve any appropriate waivers to statute or regulation. Specify any additional authority the PM may use to modify the acquisition approach without the specific approval of the MDA.

 

Authorize release of the request for proposal and related documents for development and any other MDA-approved actions.

 

Document these decisions 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 development is approved by the MDA. PM Provides: Acquisition Strategy and APB to include program requirements, schedule, activities, program funding, the assessment approach and intermediate decision points and criteria The MDA will:

  • Determine feasibility of fielding capability within required timelines to include consideration of the technical maturity of the preferred solution(s). If the MDA determines that the fielding of the capability cannot be accomplished in the required timelines, then the MDA may direct partial or interim solutions that can be fielded more rapidly, or may direct that the program will be managed under a different authority.
  • Review the acquisition strategy and program baseline and determine whether the preferred solution:
    • Can be fielded within 2 years.
    • Does not require substantial development effort.
    • Is based on technologies that are proven and available.
    • Can be acquired under a fixed price contract.
    • Provides any exceptions necessary pursuant to section 804 (b)(3) of P.L. 111-383, including exceptions to the requirements of Paragraph (2)(b)1 through Paragraph (2)(b)4 (refers to 1 thru 4 above).
  • Approve Acquisition Strategy and APB
  • Approve initial quantities to be produced and assessed, to include required assessment and training articles.
  • Decide if RRA should be requested from SECDEF or DEPSECDEF to expedite the fielding
  • Approve the planned testing approach. A normal test and evaluation master plan (TEMP) is generally not necessary.
    • TEMPs are usually not appropriate for efforts using urgent capability acquisition procedures when there is minimal development work and minimal development work and minimal test and evaluation to execute. Some test planning is usually required, however, in collaboration with the supporting developmental or operational test organization. The MDA may require a highly-tailored and abbreviated test plan. The abbreviated test plan will describe a performance assessment approach that will include schedule, test types and environment, and assets required. An Operational Test Plan for the required pre-deployment performance assessment is generally adequate. If the defense urgent capability acquisition program is under DOT&E oversight, a TEMP is also not normally required; however, the Program Manager should prepare a combined operational and live fire test plan for DOT&E approval. A TEMP is also not normally required if the urgent capability acquisition effort is under DOT&E oversight. The PM, in collaboration with the supporting operational test organization, should prepare operational and live fire test plans for DOT&E approval, however. An operational test plan for the required pre-deployment performance assessment is generally adequate.
    • Approve testing approach. If DOT&E oversight, PM prepares combined OT and live fire test plan for DOT&E approval
    • Approve any waivers to statue or regulation
    • Authorize release of RFPs
    • Document decisions in an ADM