c. Phase Description
At Milestone A, the MDA shall review the proposed materiel solution and the
draft Technology Development Strategy (TDS). The Technology Development Phase
begins when the MDA has approved a materiel solution and the TDS, and has
documented the decision in an ADM. The tables in Enclosure 4 identify all statutory and
regulatory requirements applicable to Milestone A.
The MDA for an MDAP, without the authority to delegate, shall sign a
certification memorandum for record prior to Milestone A approval (section
2366a of title 10, United States Code (U.S.C.) (Reference (k))). The memorandum shall include
the statements in 10 U.S.C. 2366a without modification. The ADM at Milestone A
shall include the statement: “I have made the certifications required by
section 2366a of title 10, United States Code.”
If, during Technology Development, the cost estimate upon which the MDA based
the Milestone A certification increases by 25 percent or more, the PM shall
notify the MDA of the increase. The MDA shall again consult with the JROC on
matters related to program requirements and the military need(s) for the
system. The MDA shall determine whether the level of resources required to
develop and procure the system remains consistent with the priority level
assigned by the JROC. If not, the MDA may rescind the Milestone A approval if
the MDA determines that such action is in the interest of national
This effort normally shall be funded only for the advanced development work.
Technology development for an MDAP shall not proceed without Milestone A
approval. For business area capabilities, commercially available solutions
shall be preferred. A favorable Milestone A decision DOES NOT mean that a new
acquisition program has been initiated.
At Milestone A, the DoD Component shall submit a cost estimate for the
proposed solution(s) identified by the AoA. If requested by the MDA, the Cost
Analysis Improvement Group (CAIG) shall develop an independent cost
Final Requests for Proposals (RFPs) for the Technology Development Phase shall
not be released, nor shall any action be taken that would commit the program
to a particular contracting strategy for Technology Development, until the MDA
has approved the TDS.
The TDS shall document the following:
The rationale for adopting an evolutionary strategy (the preferred approach)
or using a single-step-to-full-capability strategy (e.g., for common supply
items or COTS items). For an evolutionary acquisition, the TDS shall include
a preliminary description of how the materiel solution will be divided into
acquisition increments based on mature technology and an appropriate
limitation on the number of prototype units or engineering development
models that may be produced in support of a Technology Development
A preliminary acquisition strategy, including overall cost, schedule, and
performance goals for the total research and development program;
Specific cost, schedule, and performance goals, including exit criteria, for
the Technology Development Phase;
A description of the approach that will be used to ensure data assets will
be made visible, accessible, and understandable to any potential user as
early as possible (DoD Directive 8320.02 (Reference (l))).
A list of known or probable Critical Program Information (CPI) and potential
countermeasures such as anti-tamper in the preferred system concept and in
the critical technologies and competitive prototypes to inform program
protection (DoD Instruction 5200.39 (Reference (m))) and design integration
during the Technology Development Phase.
A time-phased workload assessment identifying the manpower and functional
competency requirements for successful program execution and the associated
staffing plan, including the roles of government and non-government
A data management strategy (see Section 9
in Enclosure 12).
A summary of the CAIG-approved Cost and Software Data Reporting (CSDR)
Plan(s) for the Technology Development Phase (see Section 3 in Enclosure 7).
During Technology Development and succeeding acquisition phases, the PM shall
give small business the maximum practical opportunity to participate. Where
feasible, the PM shall leverage programs which employ people with
The TDS and associated funding shall provide for two or more competing teams
producing prototypes of the system and/or key system elements prior to, or
through, Milestone B. Prototype systems or appropriate component-level
prototyping shall be employed to reduce technical risk, validate designs and
cost estimates, evaluate manufacturing processes, and refine requirements.
Information technology initiatives shall prototype subsets of overall
functionality using one or more teams, with the intention of reducing
enterprise architecture risks, prioritizing functionality, and facilitating