Acquisition Decision Memorandum (ADM)
|
•
|
•
|
|
Regulatory
|
|
|
Regulatory |
Regulatory. Documents MDA decisions and direction. Per new policy update dated Oct 20, 2022 - After approval of the program for use of the MTA pathway, the DA will sign their program ADM. The ADM signature will then start the MTA clock.
|
|
|
•
|
|
DoDi 5000.80
10 U.S.C. 4211 {formerly 2431a}
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
STATUTORY for Major systems. Regulatory for Non-major systems. The Acquisition Strategy includes STATUTORY and Regulatory information. Major changes to the plan reflected in the Acquisition Strategy require DA approval. The DA must review and approve the strategy when there has been a significant change to the cost, schedule, or performance of the program (or system) or there has been a critical change to the cost of the program (or system). The strategy may also be reviewed and approved at any time considered relevant by the DA. The following requirements will be satisfied in the Acquisition Strategy:
- ACQUISITION APPROACH
- BENEFIT ANALYSIS AND DETERMINATION, applies to bundled acquisitions only;
- BUSINESS STRATEGY;
- CONTRACTING STRATEGY, to include CONTRACT-TYPE DETERMINATION, satisfied when the DA approves the Acquisition Strategy with specified contract types, and Termination Liability Estimate;
- COOPERATIVE OPPORTUNITIES;
- GENERAL EQUIPMENT VALUATION;
- Industrial Base Capabilities Considerations;
- INTELLECTUAL PROPERTY (IP) STRATEGY, for major weapon systems and subsystems;
- MARKET RESEARCH;
- Modular Open Systems Approach (MOSA);
- MULTI-YEAR PROCUREMENT;
- PRODUCT SUPPORT, including sustainment, logistics and maintenance;
- RELIABILITY AND MAINTAINABILITY;
- RISK MANAGEMENT, including security, schedule, technical, and production risks;
- SMALL BUSINESS; INNOVATION RESEARCH (SBIR)/SMALL BUSINESS TECHNOLOGY TRANSFER (STTR) PROGRAM TECHNOLOGIES;
- Test Strategy / Assessment of Test Results;
- Transition Plan – within 2 years after MTA program start.
|
ACQUISITION APPROACH (Part of Acquisition Strategy)
|
•
|
|
10 U.S.C. 4211(c)(2)(A-B) {formerly 2431a}
|
Statutory
|
|
Statutory |
|
STATUTORY; Describe the top-level business and technical management approach in sufficient detail to allow the DA to assess (1) the viability of the approach; (2) the method of implementing laws and policies; and (3) program objectives. Provide a clear explanation of how the strategy is designed to be implemented within the available resources of time, funding, and management capacity. Discuss the tailoring that will address program requirements and constraints. Where appropriate, the strategy should consider the delivery of required capability in increments, each dependent on available, mature technology, and recognizing up front the need for future capability improvements.
|
BENEFIT ANALYSIS AND DETERMINATION (Part of Acquisition Strategy)
|
•
|
|
15 U.S.C. 644(e)(2)
15 U.S.C. 632(o)(1-2)
15 U.S.C. 657q
|
Statutory
|
|
Statutory |
|
STATUTORY. Applies to bundled acquisitions only. Includes MARKET RESEARCH to determine whether consolidation of the requirements is necessary and justified. 15 U.S.C. 632 defines a bundled contract as a contract that is entered into to meet requirements that are consolidated in a bundling of contract requirements. The term "bundling of contract requirements" means consolidating two or more procurement requirements for goods or services previously provided or performed under separate smaller contracts into a solicitation of offers for a single contract that is likely to be unsuitable for award to a small-business concern.
|
BUSINESS STRATEGY (Part of Acquisition Strategy)
|
•
|
|
10 U.S.C. 4211(c)(2)(D) {formerly 2431a}
10 U.S.C. 4324(c)(2) {formerly 2337}
|
Statutory
|
|
Statutory |
|
STATUTORY. The business strategy will describe the rationale for the contracting approach and how competition will be maintained at the system and subsystem levels throughout the program life cycle; the strategy will detail how contract incentives will be employed to support Department goals.
|
CONTRACTING STRATEGY (Part of Acquisition Strategy)
|
•
|
|
10 U.S.C. 4211(c)(2)(E) {formerly 2431a}
10 U.S.C. 3453 {formerly 2377}
41 U.S.C. 3306(a)(1) and 3307(d)
|
Statutory
|
|
Statutory |
|
STATUTORY. Discuss (1) the planned contract type and how it relates to risk management; (2) whether risk management enables the use of fixed-price elements in subsequent contracts; (3) market research; and (4) small business participation. Include the following sub-elements:
- CONTRACT-TYPE DETERMINATION
- Termination Liability Estimate
|
CONTRACT-TYPE DETERMINATION (Part of Acquisition Strategy)
|
•
|
|
§818, P.L. 109-364
§811, P.L. 112-239
10 U.S.C. 4211(c)(2)(E) {formerly 2431a}
|
Statutory
|
|
Statutory |
|
STATUTORY. Satisfied when the DA approves the Acquisition Strategy with specified contract types
|
Industrial Base Capabilities Considerations (Part of Acquisition Strategy)
|
•
|
|
DoDi 5000.60
10 U.S.C. 4211 {formerly 2440}
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
Regulatory. Summarizes the results of the industrial base capabilities' analysis.
|
INTELLECTUAL PROPERTY (IP) STRATEGY (Part of Acquisition Strategy)
|
•
|
•
|
DoDI 5010.44
10 U.S.C. 3771- 3775 {formerly 2320}
10 U.S.C. 4211 {formerly 2431a}
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
STATUTORY for Major systems and subsystems; Regulatory for Non-major systems. The IP Strategy must be updated as appropriate to support and account for evolving IP considerations associated with the award and administration of all contracts throughout the program life cycle. Becomes part of the Product Support Strategy (PSS) during Operations and Support (O&S).
|
|
International Involvement (Part of Acquisition Strategy)
|
|
|
|
Regulatory
|
|
|
Regulatory |
Regulatory. Satisfies the Statutory requirement to consider Cooperative Opportunities.
IAW 5000.80 Not all programs are appropriate for the MTA pathway. Major systems intended to satisfy requirements that are critical to a major interagency requirement, are primarily focused on technology development, or have significant international partner involvement are discouraged from using the MTA pathway.
|
MARKET RESEARCH (Part of Acquisition Strategy)
|
•
|
|
10 U.S.C. 3453 {formerly 2377}
41 U.S.C. 3306(a)(1) and 3307(d)
|
Statutory
|
|
Statutory |
|
STATUTORY. Conducted to reduce the duplication of existing technologies and products, and to understand potential materiel solutions, technology maturity, and potential sources, to assure maximum participation of small business concerns, and possible strategies to acquire them.
|
Modular Open System Approach (MOSA) (Part of Acquisition Strategy)
|
•
|
|
DoDI 5000.88
|
Regulatory
|
|
|
Regulatory |
Regulatory. Describe how a MOSA will or will not be used to evolve system capability, improve interoperability, reduce cost or schedule, and refresh technology.
|
MULTI-YEAR PROCURMENT (Part of Acquisition Strategy)
|
•
|
|
10 U.S.C. 3501 {formerly 2306b}
DoDI 5000.73
|
Statutory
|
|
Statutory |
|
STATUTORY. When appropriate, include a summary discussion of multi-year procurement (further discussed in DoDI 5000.73).
|
PRODUCT SUPPORT, including sustainment, logistics, and maintenance (Part of Acquisition Strategy)
|
•
|
|
10 U.S.C. 2464;
10 U.S.C. 2466;
10 U.S.C. 4211 {formerly 2431a}
DoDI 5000.91
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
STATUTORY. For Major systems. Content requirements of an Acquisition Strategy will ensure that each strategy will consider requirements related to product support, logistics, maintenance, and sustainment IAW 10 U.S.C. 2464 and 2466.
REGULATORY. DoD 5000.91: General Statement Up Front: Establishes policy, assigns responsibilities, and prescribes procedures for product support management to establish product support factors early in the requirements development and acquisition process to achieve effective and efficient weapon system capability and life cycle management.
Prescribes procedures for program managers (PMs), product support managers (PSMs), and life cycle logisticians (LCLs) to implement the adaptive acquisition framework (AAF) tenets to:
- Emphasize sustainment.
- Make data driven decisions.
- Tailor product support
|
RELIABILITY AND MAINTAINABILITY (Part of Acquisition Strategy)
|
•
|
•
|
10 U.S.C. 4328 {formerly 2443}
January 31, 2019 USD(A&S) Policy Memo, "Implementation of Title 10, United States Code, Section 2443, Sustainment Factors in Weapon System Design."
DoDI 5000.88
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
|
STATUTORY. For Major systems, the PM must, as part of the ACQUISITION STRATEGY:
Include measurable requirements for engineering activities and design specifications for R&M; otherwise justify in writing the determination to exclude engineering activities and design specifications for reliability or maintainability.
Indicate if sustainment factors, including R&M, are included in the process for source selection;
Describe incentive fees and penalties (as appropriate) to incentivize achievement of design specification requirements for R&M.
The DA will notify the congressional defense committees upon entering into an EMD or Production contract that includes incentive fees or penalties.
DoDI 5000.88, Section 3.b.1 For all defense acquisition programs, the LSE (lead systems engineer), working for the PM, will integrate R&M engineering as an integral part of the overall engineering process and the digital representation of the system being developed.
|
RISK MANAGEMENT (Part of Acquisition Strategy)
|
•
|
|
DoDI 5000.80
10 U.S.C. 4211 {formerly 2431a};
10 U.S.C. 4212 {formerly 2431b}
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
STATUTORY. Include a comprehensive approach to risk management and mitigation for security, schedule, technical, and production risks.
REGULATORY. DoDI 5000.80 Section 2.6. DOD AND OSD COMPONENT HEADS WITH MTA PROGRAMS. The DoD and OSD Component heads with MTA programs oversee their MTA programs through their component acquisition executives (CAEs) and program managers (PMs).
|
Test Strategy/Assessment of Test results (Part of Acquisition Strategy)
|
•
|
•
|
DoDI 5000.80
DoDI 5000.89
|
Regulatory
|
|
|
Regulatory |
Regulatory. DoD Components will develop a process for demonstrating performance and evaluating for current operational purposes the proposed products and technologies. This process will result in a test strategy or an assessment of test results documenting the evaluation of the demonstrated operational performance, to include validation of required cybersecurity and interoperability as applicable. The operational demonstration assessment will support the initial production decision by the DA. Programs on the DOT&E oversight list will follow applicable procedures.
|
Transition Plan (Part of Acquisition Strategy)
|
•
|
•
|
|
Regulatory
|
|
|
Regulatory |
Regulatory. For each MTA program, DoD Components will develop a process for transitioning successful prototypes to new or existing acquisition programs for production, fielding, and operations and sustainment under the rapid fielding pathway or other acquisition pathway. This process will result in a transition plan, included in the acquisition strategy, which provides a timeline for completion within 2 years of all necessary documentation required for transition, as determined by the DA, after MTA program start. This applies to both major and non-major programs. MTA Transition Plan Template
|
CLINGER-COHEN ACT (CCA) COMPLIANCE
|
•
|
•
|
DoDi 5000.82
SUBTITLE III, TITLE 40
§811, P.L. 106-398
|
Regulatory, Statutory
|
DA and Component CIO or designee
|
Statutory |
Regulatory |
STATUTORY for all programs that acquire information technology (IT); Regulatory for other programs. See DoDI 5000.82 for amplifying regulatory guidance. A summary of required actions is in the CCA Compliance Table. The PM will report CCA compliance to the DA and the Component CIO or designee. For IT programs employing an incremental development model, the program manager will report CCA compliance at each Limited Deployment Decision Point.
|
|
|
•
|
•
|
DoDi 8500.01
DoDi 5000.82
§811, P.L. 106-398
40 U.S.C. 11313
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
STATUTORY for mission critical and mission essential information technology programs and regulatory for all programs requiring an Authority to Operate (ATO). The Cybersecurity Strategy can serve as the System Security Plan during the Risk Management Framework process. See DoDI 8510.01 and DoDI 5000.82. The CYBERSECURITY STRATEGY is a stand-alone appendix to the Program Protection Plan (PPP). The CYBERSECURITY STRATEGY will be updated prior to receiving an ATO. The Component CIO is the approval authority.
|
DoD Component Cost Estimate
|
•
|
•
|
DoDI 5000.73
DoDI 5000.80
|
Regulatory
|
|
|
Regulatory |
Regulatory. See the direction in DoDI 5000.80 and DoDI 5000.73. The DoD Component will determine the cost estimating requirements for Major systems and below.
|
|
|
•
|
•
|
|
Regulatory
|
|
|
Regulatory |
Regulatory. Exit criteria are specific events and accomplishments that must be achieved before a program can proceed; documented in the ADM.
|
FREQUENCY ALLOCATION APPLICATION (DD FORM 1494)
|
•
|
•
|
§104, P.L. 102-538
47 U.S.C. 305, 901-904
|
Statutory
|
National Telecommunications and Information Administration (NTIA)
|
Statutory |
|
STATUTORY for all systems/equipment that use the electromagnetic spectrum while operating in the United States and its possessions. The DD Form 1494, Application for Equipment Frequency Allocation, is available from https://www.esd.whs.mil/Directives/forms/dd1000_1499/
The Title 47 STATUTORY requirement is satisfied when the NTIA has authorized national spectrum certification(s) for the program at Stage 1, 2, 3 or 4, as applicable, in response to submitted DD Form(s) 1494 by the program manager.
|
Full Funding Certification Memorandum
|
•
|
•
|
|
Regulatory
|
|
|
Regulatory |
Regulatory. See DoDI 5000.73 for details, including coordination requirements.
|
Independent Cost Estimate (ICE)
|
•
|
•
|
10 U.S.C. 4323 {formerly 2441}
DoDI 5000.73
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
|
Regulatory. DoDI 5000.73 provides detailed instructions.
(1) Rapid Prototyping Programs. CAPE will conduct an estimate of life-cycle costs for programs likely to exceed acquisition category (ACAT) I threshold pursued using the MTA rapid prototyping pathway. CAPE may, in its discretion, delegate the authority for the conduct of the cost estimate to the SCA. Estimates for rapid prototyping programs that do not exceed the ACAT I threshold must be conducted in accordance with guidance issued by the relevant SCA.
(2) Rapid Fielding Programs. CAPE will conduct an estimate of life-cycle costs for programs likely to exceed ACAT I or II thresholds pursued using the MTA rapid fielding pathway. CAPE may, in its discretion, delegate the authority for the conduct of the cost estimate to the SCA. DoD Components must conduct life-cycle cost estimates for rapid fielding programs that do not exceed the ACAT II threshold in accordance with guidance issued by the relevant SCA.
|
Information Support Plan (ISP)
|
•
|
•
|
DoDI 8330.01
DoDI 8320.02
DoDI 8410.03
|
Regulatory
|
DoD Component or as delegated
|
|
Regulatory |
Regulatory. Applicable to all IT, including NSS. An updated ISP of record may be required during O&S. Enter data on-line at https://gtg.csd.disa.mil/ (requires an account and login with CAC).
|
Information Technology and National Security System Interoperability Certification
|
•
|
•
|
DoDI 5000.80
DoDI 8330.01
|
Regulatory
|
|
|
Regulatory |
Regulatory. Applicable to all IT, including NSS. Testing completed before or during OT&E. The Joint Interoperability Test Command (JITC) certifies interoperability of IT with joint, multinational, and/or interagency interoperability requirements. DoD Components certify all other IT. Certification must occur prior to deployment.
|
|
LIFECYCLE SUSTAINMENT PLAN (LCSP)/PRODUCT SUPPORT STRATEGY (PSS)
|
•
|
•
|
10 U.S.C 4324 {formerly 2337}
DoDI 5000.80
DoDI 5000.91
|
Regulatory, Statutory
|
|
Statutory |
Regulatory |
STATUTORY for “covered systems” before a decision to enter into system development and demonstration. The LCSP/PSS satisfies the statutory requirements of Section 4324 of Title 10 U.S.C. See DoDI 5000.91 for details about the LCSP/PSS . The PSM will support the PM in developing and implementing the LCSP/PSS (or a tailored LCSP for non-covered systems). The LCSP/PSS has required annexes that are reflective of the program's latest planned and completed activities tied to a program's life-cycle sustainment that correlate with statute.
The following requirements will be satisfied in the LCSP/PSS:
- PRODUCT SUPPORT BUSINESS CASE ANALYSIS—The BCA and the cost-benefit analyses (CBA) satisfies statutory requirement to conduct appropriate cost, risk, and trades analyses to validate the product support strategy.
- CORE LOGISTICS DETERMINATION
- IP STRATEGY—prepared for the acquisition strategy.
- PRESERVATION AND STORAGE OF UNIQUE TOOLING PLAN
- PROGRAMMATIC, ENVIRONMENT, SAFETY, AND OCCUPATIONAL HEALTH (ESOH) (PESHE)
- REPLACED SYSTEM SUSTAINMENT PLAN
- SOFTWARE PRODUCT SUPPORT STRATEGY
- System Disposal Plan
|
PESHE AND NEPA/E.O. 12114 COMPLIANCE SCHEDULE (Part of LCSP/PSS)
|
•
|
•
|
42 U.S.C. 4321-4347
E.O. 12114
|
Statutory
|
|
Statutory |
|
STATUTORY. The Programmatic Environment, Safety, and Occupational Health Evaluation (PESHE) and National Environmental Policy Act (NEPA) / Executive Order (E.O.) 12114 Compliance Schedule is approved by the DA or designee. Related design considerations must be included in the SEP; related operations or sustainment considerations will be included in the PSS.
|
Program Protection Plan (PPP)
|
•
|
•
|
DoDI 5200.39
DoDI 5200.44
|
Regulatory
|
|
|
Regulatory |
Regulatory. If applicable, after the Full Rate Production or Full Deployment decision, the PPP will transition to the PM responsible for system sustainment and disposal. The PPP includes appropriate appendixes or links to required information. The official designated by the DoD Component head will be the approval authority.
|
Request for Proposal (RFP)
|
•
|
•
|
Federal Acquisition Regulation (FAR) Subpart 15.203
|
Regulatory
|
|
|
Regulatory |
Regulatory. RFPs are issued as necessary; they include specifications, deliverable lists, and statement of work. See also Defense Federal Acquisition Regulation Supplement (DFARS) subpart 201.170 and Class Deviation 2019-O00010, dated August 20, 2019, for peer review requirements. For acquisitions where government property will be provided to a contractor for the performance of a contract, a business case analysis must be performed, demonstrating it is in the government's best interest to provide government property, otherwise the contract could not be performed. In addition, the solicitation and ensuing contract must have the appropriate government property clause and mandatory clauses incorporated. SOURCE: FAR 45.102.b and DFARS 245.103-70.
|
|
|
•
|
|
|
Statutory
|
|
Statutory |
|
SRs begin 5 years after initial operational capability and repeat every 5 years thereafter. Statute only requires sustainment reviews for an MTA program that meets or breaches the MDAP dollar threshold. Submitted to Congress by 30-Sep of the fiscal year conducted.
|
Systems Engineering Plan (SEP)
|
•
|
•
|
|
Regulatory
|
|
|
Regulatory |
Regulatory. The DA, or designee, is the approval authority. The SEP should be approved before each release of Requests for Proposal (RFP) involving prototyping, technology maturation, risk reduction, engineering and manufacturing development, or production contracts. The SEP will be updated after contract award, if needed. A SEP outline is available at https://ac.cto.mil/engineering/.
|
