STATUTORY for MDAPs and major subprograms of MDAPs before Milestone A approval.  By this table, the MDA does not have authority to delegate this requirement.  As part of the "4251 WRITTEN DETERMINATION," the MDA must determine that the Chief and the Secretary concur with the cost, schedule, technical feasibility, and performance trade-offs that have been made.  Additional criteria for the WRITTEN DETERMINATION are in the source statute; implementation details are in the current version of Under Secretary of Defense for Acquisition, Technology and Logistics USD(AT&L) Memorandum (now USD(A&S)), "Change to Major Defense Acquisition Program Milestone A Requirements."  Full 10 U.S.C. 4251 Milestone A compliance requires the MILESTONE SUMMARY REPORT in the Recurring Program Reports Table.

STATUTORY for MDAPs before Milestone B approval.  The MDA does not have authority to delegate this requirement.  The certification and determination will be submitted to the congressional defense committees with the first Selected Acquisition Report (SAR) submitted after completion of the certification, and the MDA will retain records of the basis for the certifications and determination.  As part of the "4252 CERTIFICATION AND DETERMINATION," the MDA must determine that the Chief and the Secretary concur with the cost, schedule, technical feasibility, and performance trade-offs that have been made.  Additional criteria for the CERTIFICATION AND DETERMINATION are in the source statute; implementation details are in the current version of USD(AT&L) Memorandum (now USD(A&S)), "Change to Major Defense Acquisition Program Milestone B Requirements."  A memorandum documenting the certification and determination elements is a Regulatory requirement at Milestone C if "C" is program initiation.  Full 10 U.S.C. 4252 Milestone B compliance requires the MILESTONE SUMMARY REPORT in the Recurring Program Reports Table.
 

STATUTORY; describe the top-level business and technical management approach in sufficient detail to allow the MDA 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.  
 

Regulatory.  Documents MDA decisions and direction.

STATUTORY for MDAPs at Milestones B and C and the FRP decision; a Regulatory requirement at all other Program Type/Event combinations, including the required draft at Development RFP Release.  For the APB, the draft due at RFP Release does not require CAE approval.  The APB is not approved by the MDA until Milestone B.  See the introductory text for the Acquisition Program Baselines Table and the Statutory Program Breach Definitions Table for requirements at other than the identified decision points.

STATUTORY for MDAPs and major systems (including AIS programs that exceed the dollar thresholds for a "major system," as identified in DoDI 5000.85, Appendix 3A); Regulatory for other programs.  The Acquisition Strategy includes STATUTORY and Regulatory information.  Major changes to the plan reflected in the Acquisition Strategy require MDA approval.  If the MDA revises the strategy for an MDAP or major defense subprogram because of a significant or critical change to the cost of the program or system, or a significant change to the schedule or performance of the program or system, the MDA must notify the congressional defense committees consistent with the Exceptions, Waivers, and Alternative Management and Reporting Requirements Table.  The MDA 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 MDA.  The following STATUTORY requirements will be satisfied in the Acquisition Strategy:  

ACQUISITION APPROACH, BENEFIT ANALYSIS AND DETERMINATION; BUSINESS STRATEGY; CONTRACTING STRATEGY, TO INCLUDE CONTRACT-TYPE DETERMINATION and TERMINATION LIABILITY ESTIMATE; COOPERATIVE OPPORTUNITIES; GENERAL EQUIPMENT VALUATION;INDUSTRIAL BASE CAPABILITIES CONSIDERATIONS; INTELLECTUAL PROPERTY (IP) STRATEGY; MARKET RESEARCH; MODULAR OPEN SYSTEMS APPROACH (MOSA);  MULTI-YEAR PROCUREMENT; PRODUCT SUPPORT (INCLUDING SUSTAINMENT, LOGISTICS, AND MAINTENANCE; RELIABILITY AND MAINTAINABILITY); PROGRAM INTEGRATION OF INTELLIGENCE ASSESSMENTS; RISK MANAGEMENT; SMALL BUSINESS; INNOVATION RESEARCH (SBIR)/SMALL BUSINESS TECHNOLOGY TRANSFER (STTR) PROGRAM TECHNOLOGIES. For details regarding each of these Information Requirements, go to the respective entry in this Table (if applicable, based on filtering selection).

Regulatory.  Affordability analysis will be conducted prior to Milestone A (or Milestone B, if "B" is the initial milestone) and updated if program funding changes dictate a reassessment of affordability.  The Affordability Analysis is used, in part, to support the development of programs goals pursuant to 10 U.S.C. 4271 and further described in DoDI 5000.85.

STATUTORY for MDAPs at Milestone A through Milestone B.  The DoD Component is responsible for performing the AoA consistent with the study guidance developed by the Director, Cost Assessment and Program Evaluation (DCAPE) and the study plan approved by DCAPE.  DoDD 5105.84 details the responsibility of DCAPE for AoAs. 

Regulatory requirements to guide the AoA.  AoA Study Guidance informs the preparation of the AoA Study Plan.  DCAPE will develop and issue the AoA Study Guidance for all MDAPs.  AoA Study Guidance must be provided to DoD Component(s) for development of the AoA Study Plan, which the DoD Components submit to DCAPE for approval.
 

STATUTORY for MDAPs and major weapon systems; Regulatory for all other programs.  Bandwidth requirements data will be documented in the Information Support Plan (ISP).  If the ISP is waived for a program, conformance with bandwidth review will be based on data provided in the Capability Development Document (CDD), consistent with the Net-Ready guidance in Appendix C to Enclosure B of the Manual for the Operation of the Joint Capabilities Integration and Development System (JCIDS) and Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 5123.01I.

STATUTORY; applies to bundled acquisitions only.  Includes MARKET RESEARCH to determine whether consolidation of the requirements is necessary and justified.  Required at Milestone C, if there was no Milestone B; an update is not required at the FRP decision point.  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.  
 

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.  

Regulatory.  A draft CDD is required at Milestone A; a validated CDD is required at the Development RFP Release Decision Point and informs Milestone B.  If a requirements change is needed prior to Milestone C, the CDD will be updated and revalidated.  An equivalent DoD Component-validated requirements document will satisfy the CDD requirement for certain information systems.  For approval authorities, JROC is Joint Requirements Oversight Council; JCB is Joint Capabilities Board.
 

STATUTORY for all programs that acquire information technology (IT); Regulatory for other programs.  See DoDI 5000.82 for amplifying regulatory policy.  A summary of required actions is in the CCA Compliance Table.  The PM will report CCA compliance to the MDA and the Component CIO or designee.  For IT within an MCA program employing an incremental development model, the program manager will report CCA compliance at each Milestone and/or Limited Deployment Decision Point for the IT.

Regulatory.  The CONOPS/OMS/MP is a Component-approved document that is derived from and consistent with the validated/approved capability requirements document.  The CONOPS/OMS/MP describes the operational tasks, events, durations, frequency, and environment in which the materiel solution is expected to perform each mission and each phase of the mission.  The CONOPS/OMS/MP will be provided to the MDA at the specified decision events and normally provided to industry as part of the RFP.

STATUTORY.  Satisfied when the MDA approves the Acquisition Strategy with specified contract types.  Only required for MDAPs at Development RFP Release and Milestones B and C.  The MDA for an MDAP may conditionally approve the contract type selected for a development program at the Development RFP Release Decision Point, and give final approval at the time of Milestone B approval.  The development contract type must be consistent with the level of program risk and may be either a fixed price or cost type contract.  If selecting a cost-type contract or a contract utilizing certain incentive provisions, the MDA must comply with the conditions and reporting requirements listed in the Exceptions, Waivers, and Alternative Management and Reporting Requirements Table.  The DoD MAY NOT enter into cost-type contracts for production of an MDAP unless compliant with the conditions and notifications listed in the Exceptions, Waivers, and Alternative Management and Reporting Requirements Table.  
 

STATUTORY; discuss (1) the planned contract type and how it relates to risk management in each acquisition phase; (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 

STATUTORY.  Due at the first program milestone review.  The requirement to discuss opportunities for cooperative research and development will be satisfied via the International Involvement section in the Acquisition Strategy outline and will include consideration of foreign military sales.  For programs responding to urgent needs, proven capabilities will be assessed during the COURSE OF ACTION ANALYSIS. 
 

STATUTORY.  Only the CORE LOGISTICS DETERMINATION is required at Milestone A.  Required at Milestone C if there was no Milestone B.  Documented in the PSS.    By Milestone A, the PM with support of the DoD Component will document its determination of applicability of core depot-level maintenance and repair capability requirements in the PSS.  For Milestone B, the PM with support of the DoD Component will attach the program's estimated requirements for maintenance, repair, and workloads to the PSS.  The program's maintenance planning will ensure that core depot-level maintenance and repair capabilities and capacity are established NLT 4 years after IOC.  The PM will ensure that a depot source of repair designation is made NLT 90 days after the Critical Design Review.  See the PSS row, this table. Not required for AIS programs.

Regulatory.  Procedures are specified in DoDI 5000.73.  DoDI 5000.73 provides CAPE the authority to assess the sufficiency of the CARD prior to DoD Component approval. The DoD Component, with CAPE concurrence, will determine the CARD requirements for ACAT II and below programs.

STATUTORY for mission essential and mission critical technology and a regulatory requirement for all technology, including national security systems. The CYBERSECURITY STRATEGY reflects both the program's long-term approach for, and implementation of cybersecurity throughout the program lifecycle. The CYBERSECURITY STRATEGY is a tool for Program Managers, Authorizing Officials, and relevant review and approval authorities to plan for, identify, assess, mitigate, and manage cybersecurity risks across a system's lifecycle. See DoDI 8500.01, DoDI 8510.01, and DoDI 5000.82. The CYBERSECURITY STRATEGY is a stand-alone appendix to the Program Protection Plan (PPP). Cybersecurity personnel and program management offices need to begin drafting a Cybersecurity Strategy, as soon as possible, in the Material Solutions Analysis phase. The CYBERSECURITY STRATEGY, as approved by the cognizant Chief Information Officer, is initially due before Milestone A. The CYBERSECURITY STRATEGY will be updated, as needed, at each lifecycle phase and prior to receiving an ATO. The DoD CIO is approval authority for MCA ACAT ID programs; the Component CIO is approval authority for all other ACATs / acquisition pathways. After systems are authorized, the CYBERSECURITY STRATEGY joins the system authorization as an artifact and is updated as necessary to prepare for the upcoming system re-authorization activities, as needed.

See the Major Capability Acquisition Pathway Integration with Risk Management Framework guidance as published on the DoD CIO Library for more information about integrating cybersecurity, acquisitions, and test and evaluation processes.
 

Regulatory.  The Depot Source of Repair (DSOR) determination process applies to any program with an approved JCIDS capability requirements document when the APB is approved. Initial DSOR assignments are determined jointly between the Military Departments and the Office of the USD(A&S) for ACAT III and above programs.

No later than 90 calendar days after the critical design review or equivalent, the designated authority will approve the DSOR Certification and Determination.  The resulting DSOR assignments will be documented in the next update of the PSS, but no later than Milestone C or equivalent programmatic decision.  10 U.S.C Chapter 146 provides statutory language related to maintenance and repair activity. 

Regulatory.  Requirements and procedures for this assessment are specified in DoDI 5000.73.

Regulatory.  See the direction in DoDI 5000.73.  The DoD Component will determine the cost estimating requirements for ACAT II and below programs.

Regulatory.  Mandatory for MDAPs; documented DoD Component Cost Position must be signed by the appropriate DoD Component Deputy Assistant Secretary for Cost and Economics (or Defense Agency equivalent) and include a date of record.

Regulatory.  Programs on the Director, Operational Test and Evaluation (DOT&E) Oversight List for LFT&E oversight only; due upon completion of LFT&E.

STATUTORY; required for DOT&E Oversight List programs only.  The DOT&E publishes an online list of programs under operational test and evaluation (OT&E) and LFT&E oversight at https://osd.deps.mil/org/dote-extranet/SitePages/Home.aspx (requires login with a Common Access Card (CAC)).

A final decision to proceed beyond Low-Rate Initial Production (LRIP) or beyond Limited Deployment may not be made until the DOT&E has submitted the IOT&E Report to the Secretary of Defense, and the congressional defense committees have received that report.  If DoD decides to proceed to operational use of the program or to make procurement funds available for the program before the MDA's FRP decision, the DOT&E's report will be submitted as soon as practicable after the DoD decision to proceed.

STATUTORY: D(DT&E) will conduct the MS B and MS C DT&E sufficiency assessments for MDAPs for which the USD(A&S) is the MDA and report the DT&E sufficiency assessment determinations to the USD(A&S).  The senior official within their Military Department, Defense Agency, or DoD Field Activity with responsibility for DT&E will conduct the MS B and MS C DT&E sufficiency assessments for MDAPs for which the MDA is the Service or Component Acquisition Executive.

Regulatory.  Exit criteria are specific events and accomplishments that must be achieved before a program can proceed to the designated acquisition phase covered by the criteria; documented in the ADM.

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/DD1494/.  The Title 47 STATUTORY requirement for DoD milestone decision 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.

Regulatory.  See DoDI 5000.73 for details, including coordination requirements.

STATUTORY; a program description that identifies contract-deliverable equipment items to include weapon systems, non-weapon systems, and other deliverable items; includes plan(s) to ensure that all deliverable equipment requiring capitalization is serially identified and valued.  Only required at Milestone C; updated as necessary for the FRP Decision.  The capitalization thresholds are unit costs at or above $1 million for Air Force and Navy general fund assets, and unit costs at or above $250 thousand for all internal use software and for other equipment assets for all other general and working capital funds.  Ensure all contracts and contract systems are compliant with Financial Improvement and Audit Readiness (FIAR) requirements. 

STATUTORY for MDAPs. DoDI 5000.73 provides detailed instructions.

STATUTORY for weapon system MDAPs only.  Recurs NLT every 5 years after IOC.  DoDI 5000.91 and the Independent Logistics Assessment Guidebook provide additional detail.  Must be completed prior to key acquisition decision points including Milestones B and C and the FRP Decision.  Results of the assessment will be reported to the Assistant Secretary of Defense (Sustainment) via the OSD Acquisition Information Repository (AIR).

STATUTORY.  ITRAs will be conducted on all MDAPs prior to Milestone A approval, Milestone B approval, and any decision to enter into low-rate initial production or full rate production.  ITRAs may also be conducted at the direction of the Secretary or Deputy Secretary.  USD(R&E) will conduct and approve ITRAs for ACAT ID programs.  Components will conduct ITRAs on ACAT IB/IC programs.  USD(R&E) will determine ITRA approval authority for ACAT IB/IC programs.  The DoD ITRA Framework for Risk Categorization Guide and DoD ITRA Execution Guidance provide additional information.  ITRAs inform the 10 U.S.C 4251, 4252, and 4253 requirements.  For programs for which an ITRA is conducted, a separate Technology Readiness Assessment (TRA) report is not required. Additional policy associated with ITRAs is included in the Engineering Instruction, DoDI 5000.88.

STATUTORY for MDAPs; Regulatory for others.  Summarizes the results of the industrial base capabilities' analysis.  
 

Regulatory.  Applicable to all IT, including NSS.  A draft⁴ is due for Development RFP Release; approved at Milestone B.  Unless waived, the plan is updated at the Critical Design Review.  The ISP of record is due prior to Milestone C; 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).

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.

Regulatory.  The ICD is the fundamental requirements document establishing validated capability requirements; required for the MDD.

Regulatory.  Design considerations related to unique identification are included in the Systems Engineering Plan (SEP).

STATUTORY.  A covered system may not proceed beyond LRIP until realistic survivability testing of the system is completed and the report is submitted to the Secretary of Defense and the congressional defense committees. A major munition program or a missile program may not proceed beyond LRIP until realistic lethality testing of the program is completed and the report is submitted to the Secretary of Defense and the congressional defense committees.

Regulatory; only required if the system is dependent on Intelligence Mission Data.  A draft⁴ update is due for Development RFP Release; approved at Milestone B.

STATUTORY for MDAPs and ACAT II programs; Regulatory for other programs.  A preliminary quantity is determined at the Development RFP Release Decision Point; the final LRIP quantity is determined at Milestone B.  The LRIP quantity will be documented in the ADM.  For programs on the DOT&E Oversight List, LRIP quantities must equal or exceed the numbers required for testing as identified in the approved Test and Evaluation Master Plan (TEMP).

STATUTORY.  A stand-alone Regulatory requirement at MDD.  STATUTORY updates (as part of the ACQUISITION STRATEGY) required at Milestone A and the Development RFP release point; not required thereafter.  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.  For programs responding to urgent needs, included in the Course of Action Approach at the Development Milestone.  

Regulatory.  Applicable to all programs that require MEPS equipment.  PMs will coordinate through their Service MEPS Office in accordance with DoDI 4120.11. DoDI 4120.11 establishes the principal policy associated with DoD MEPS management.

STATUTORY for MDAPs; Regulatory for other programs.  Describe how a MOSA will or will not be used to evolve system capability, improve interoperability, reduce cost or schedule, and refresh technology.  Planning will be consistent with the discussion in DoDI 5000.85, Para. 3C.3.a.(5).   

STATUTORY; when appropriate, include a summary discussion of multi-year procurement (further discussed in DoDI 5000.73).   

Regulatory. Applicable to all programs producing or using positioning, navigation, and timing (PNT) information. The MDA confirms that the program has complied with procedures identified in DoDI 4650.08, including planned testing and evaluation.

Regulatory.  Required earlier than the FRP decision if early operational assessments or operational assessments are conducted.

STATUTORY/Regulatory.  An OTP, approved before the start of OT&E, is mandatory for all programs.  Approval by DOT&E is a STATUTORY requirement for programs on the DOT&E Oversight list.  DoD Component-equivalent approval is a Regulatory requirement for all other programs. 

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 MDA or designee.  Related design considerations must be included in the SEP; related operations or sustainment considerations after Milestone C will be included in the PSS.

STATUTORY.  Responds to statute that requires Federal Agencies to compare actual program results with established performance objectives.  The PIR is a process that aggregates information needed to successfully evaluate the degree to which a capability has been achieved.  The preparation of the TEMP and the MDA's decision to proceed with FRP satisfy the requirement for weapons systems.  DoD Components will plan, conduct, and document the required review for IT systems and NSS post IOC.  Approval by the Functional Sponsor will require coordination with the Component CIO.

STATUTORY.  Part of the PSS.  The MDA must approve the plan prior to Milestone C approval; updated only as necessary thereafter.  The plan must identify any contract clauses, facilities, and funding required to preserve and to store the unique tooling associated with the production of the MDAP hardware through the end of the service life of the end item.  See paragraph 4.11.g in DoDI 5000.91 for details; see also PSS row, this table.

STATUTORY.  For MDAPS, major systems, and business 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.  

STATUTORY for major weapon systems to include MDAPs; Regulatory for other program types.  A draft⁴ update is due for Development RFP Release; approved at Milestone B.  The PSS (including Life Cycle Sustainment Plans (LCSP)) satisfies the statutory product support strategy requirement of Section 4324 of Title 10 U.S.C.  USD(A&S), or as designated, will approve the PSS for an ACAT ID program and a USD(A&S)-designated business system or special interest program.  The CAE, or designee, will approve PSSs for ACAT IB, ACAT IC, or below programs.  See DoDI 5000.91 for details about the PSS.  The PSS has required annexes that are reflective of the program's latest planned and completed activities that correlate with statute, with the product support strategy, as well as with statutory and regulatory requirements tied to a program's life-cycle sustainment.

• PRODUCT SUPPORT BUSINESS CASE ANALYSIS - STATUTORY. 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.  In support of the Milestone entry decision, the BCA or CBA is required to validate and then revalidate the product support strategy over the life cycle per 10 U.S.C. 4324 and DoDI 5000.91.   SOURCES: 10 U.S.C. 4324.
• CORE LOGISTICS ANALYSIS - STATUTORY. Described in this table and in DoDI 5000.91.
• IP STRATEGY - STATUTORY.  References the IP Strategy in the ACQUISITION STRATEGY.
• PRESERVATION AND STORAGE OF UNIQUE TOOLING PLAN - STATUTORY.  Described in this table and in DoDI 5000.91. 
• PROGRAMMATIC, ENVIRONMENT, SAFETY, AND OCCUPATIONAL HEALTH (ESOH) (PESHE) - STATUTORY.  Described in this table and in DoDI 5000.88.  The PESHE originates in the SEP and by Milestone C, becomes an annex to the PSS to describe the program's ESOH risk and requirements management in the system's design, development, testing, training, fielding, deployment, operation, maintenance, and disposal.  SOURCE: NEPA, E.O.12114.
• REPLACED SYSTEM SUSTAINMENT PLAN - STATUTORY. Described in this table.
• SOFTWARE PRODUCT SUPPORT STRATEGY - STATUTORY. Included in the PSS as a section or as a separate annex and updated appropriately throughout the program life cycle.  Requirements to continuously operate the software capabilities over the program life cycle will be documented in the PSS.  Software life cycle management will be coordinated in accordance with the USD(A&S) Software Acquisition Pathway Policy Letter.  SOURCES: 10 U.S.C. 4324, 4146, and 2474; DoDIs 4151.20 and 5000.87.
• System Disposal Plan - Regulatory.  By Milestone C, the system disposal plan will be included in the PSS and updated throughout the program life cycle.  SOURCES: 10 U.S.C. 4252, DoDI 4160.28, DoD 4160.21-M, DoD 4160.28-M and DoDI 5000.91.

STATUTORY.  The MDA must establish program cost, fielding, and performance goals (also called targets) before funds are obligated for technology development, systems development, or production of an MDAP.  These goals will replace affordability goals and caps for MDAPs proceeding through Milestone A (or the initial milestone event) after October 1, 2017.

* (Other) If following Milestone A, the estimated procurement unit cost for the program or the estimated date for IOC for the baseline description for the program exceeds the program cost or fielding targets established by the MDA, the MDA will re-assess the program and, if justified, increase the program cost target and/or increase the fielding target prior to the next milestone or production decision in consultation with OSD advisors.  The new goals must be approved before the program can proceed through a milestone event. 

Regulatory.  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. For all programs under USD(A&S) oversight, the office of the USD(R&E) will be the approval authority for the PPP; for all other ACATs, the official designated by the DoD Component head will be the approval authority.

• STATUTORY; For MDAPs and Major Systems, the PM must, as part of the ACQUISITION STRATEGY:
  • Include measurable requirements for engineering activities and design specifications for R&M for TMRR, EMD and Production solicitations; otherwise justify in writing the determination to exclude engineering activities and design specifications for reliability or maintainability from the solicitation.
  • 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 in all EMD and Production solicitations and contracts.
• The MDA will notify the congressional defense committees upon entering into an EMD or Production contract that includes incentive fees or penalties.

STATUTORY.  May be submitted as early as Milestone A, but no later than Milestone B.  Required when an MDAP replaces an existing system and the capability of the old system remains necessary and relevant during fielding of and transition to the new system.  The plan must provide for the appropriate level of budgeting for sustainment of the old system, the schedule for developing and fielding the new system, and an analysis of the ability of the existing system to maintain mission capability against relevant threats.  Is an annex to the PSS.

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. When the DAE is the MDA, the peer review, as described in the Defense Federal Acquisition Regulation Supplement subpart 201.170, will be conducted and provide the basis for the PM's recommendation for RFP approval to the MDA. 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.  ADDITIONAL SOURCES:  FAR 45.102.b and DFARS 245.103-70.

STATUTORY; include a comprehensive approach to risk management and mitigation.  Planning will be consistent with the risk management and competitive prototyping discussions in DoDI 5000.85.  If prototyping is not used, explain why.

Regulatory.  "Should cost" is a regulatory tool designed to proactively target cost reduction and drive productivity improvement into programs.  Paragraph 3C.3.c.(2) in Appendix 3C of DoDI 5000.85 provides additional detail on "Should Cost."

STATUTORY. PMs will establish goals for applying SBIR and STTR technologies in programs of record and incentivize primes to meet those goals. For contracts with a value at or above $100 million, PMs will establish goals for the transition of Phase III technologies in subcontracting plans and require primes to report the number and dollar amount of Phase III SBIR or STTR contracts. Not required at Milestone B.

Regulatory.  Applicable to all systems/equipment that use the electromagnetic spectrum in the United States and in other host nations.  Due at milestone reviews and prior to requesting authorization to operate (for other than testing) in the United States or in host nations.

STATUTORY.  Component Secretaries will conduct a SUSTAINMENT REVIEW (SR) of each MDAP and major weapon system no less than every 5 years after declaration of a program's/ system's IOC and throughout the program life cycle to assess the product support strategy, performance, and O&S costs of the weapon system.  The results of the SR will be documented in a memorandum by the relevant decision authority.  The Secretary concerned will make the memorandum and supporting documentation for each SR available to the USD(A&S) within 30 days after the review is completed.  The Secretary concerned will use availability and reliability thresholds and cost estimates as the basis for the circumstances that prompt such a review. 

Regulatory.  The MDA, or designee, is the approval authority for ACAT IB/IC SEPs, and below.  The SEP approval authority for ACAT ID programs will be USD(R&E).  The SEP will be approved before each release of acquisition 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 SEP-Outline-4.1.pdf (cto.mil). Guidance is available at Engineering of Defense Systems Guidebook (cto.mil).  

STATUTORY. For programs for which an ITRA is conducted, a Technology Readiness Assessment (TRA) report is not required.  Programs will continue to assess and document the technology maturity of all critical technologies consistent with the TRA Guidance.

Regulatory.  Prepared by the DoD Component and coordinated with the DoD Component intelligence analytical centers per DoDI O-5240.24.  Forms the analytic foundation for counterintelligence assessments in the associated PPP.  DIA will validate the report for ACAT ID; the DoD Component will be the validation authority for ACATs IB, IC, and below.

STATUTORY.  Only for MDAPs.  Must be documented in the ACQUISITION STRATEGY for any contract for the development or production of an MDAP for which potential termination liability could reasonably be expected to exceed $100 million.  Updates may therefore be required at other than the marked events.  The estimate must include how such termination liability is likely to increase or decrease over the period of performance.  The PM must consider the estimate before making recommendations on decisions to enter into or terminate such contracts.   

Regulatory.  A draft⁴ update is due for the Development RFP Release Decision Point; approved at Milestone B.  DOT&E will co-approve the TEMP for DOT&E Oversight programs (DoDD 5141.02); the DoD Component OT authority will approve the OT portion of the TEMP for all other programs.  The approval of the DT&E plan within the TEMP will be consistent with the procedures specified in the Test and Evaluation Instruction.  The TEMP outline guidance for OT&E is located at https://osd.deps.mil/org/dote-extranet/SitePages/Home.aspx. The TEMP guidance for DT&E content is included in the Test and Evaluation Enterprise Guidebook.

Regulatory.  MDAPs require a unique system-specific VOLT report to support capability development and PM assessments of mission needs and capability gaps against likely threat capabilities at IOC.  The VOLT report uses the bi-annual Defense Intelligence Threat Library Threat Modules as its analytic foundation.  The threat modules provide the PM projections of technology and adversary capability trends for the next 20 years.  VOLT reports are required for all other programs unless waived by the MDA.  In conjunction with the VOLT, the requirements sponsor and Component capability developer will collaboratively develop critical intelligence parameters in accordance with the JCIDS.  Programs on the DOT&E Oversight List require a unique, system-specific VOLT, unless waived by both the MDA and the DOT&E.  DoD Components produce a VOLT.  DIA validates the VOLT for ACAT ID programs; the DoD Component validates the VOLT for ACAT IB and IC programs and below. 

Regulatory.  Application to the DoD CIO for approval of the development or modification of waveforms.  Required at Milestone C, FRP, and any time post FRP if a waveform is added or modified after Milestone B.