Skip Ribbon Commands
Skip to main content
 
      

Air Force Examples

Examples of Documents Required for Milestone/Decision Reviews - PM Related

This site contains examples of statutory required documents and reports applicable to MDAPs and MAIS acquisition programs. These are documents that are generated by the PM office.

Please note that many of these examples are from the Air Force and they are provided for your guidance, and that the other services or agencies may or may not have different documentation requirements.

  
  
Topic Area
  
Organization
  
  
ACC Topic
  
Summary Description
  
  
Acquisition Decision Memorandum ADM FRP Decision ADDM Template v 1.4.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Defense Acquisition Guidebook (DAG) Chapt 3: “Affordability & Life Cycle Resource Estimates” dated 15 May 2013

ADDM Application link

Guidance:
A memorandum signed by the Milestone Decision Authority (MDA) that documents decisions made as the result of a Milestone Decision Review (MDR) or other decision or program review.
 
BofV
5/18/2017 7:46 PM
Acquisition Decision Memorandum ADM MDD ADDM Template v 1.4.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Defense Acquisition Guidebook (DAG) Chapt 3: “Affordability & Life Cycle Resource Estimates” dated 15 May 2013
ADDM Application link
Guidance:
A memorandum signed by the Milestone Decision Authority (MDA) that documents decisions made as the result of a Milestone Decision Review (MDR) or other decision or program review.
BofV
5/18/2017 7:46 PM
Acquisition Decision Memorandum ADM MS A ADDM Template v 1.4.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Defense Acquisition Guidebook (DAG) Chapt 3: “Affordability & Life Cycle Resource Estimates” dated 15 May 2013
ADDM Application link
Guidance:
A memorandum signed by the Milestone Decision Authority (MDA) that documents decisions made as the result of a Milestone Decision Review (MDR) or other decision or program review.
BofV
5/18/2017 7:46 PM
Acquisition Decision Memorandum ADM MS B ADDM Template v 1.4.docx
  
EngineeringAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Defense Acquisition Guidebook (DAG) Chapt 3: “Affordability & Life Cycle Resource Estimates” dated 15 May 2013
ADDM Application link
Guidance:
A memorandum signed by the Milestone Decision Authority (MDA) that documents decisions made as the result of a Milestone Decision Review (MDR) or other decision or program review.
BofV
5/18/2017 7:46 PM
Acquisition Decision Memorandum ADM MS C ADDM Template v 1.4.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Defense Acquisition Guidebook (DAG) Chapt 3: “Affordability & Life Cycle Resource Estimates” dated 15 May 2013
ADDM Application link
Guidance:
A memorandum signed by the Milestone Decision Authority (MDA) that documents decisions made as the result of a Milestone Decision Review (MDR) or other decision or program review.
BofV
5/18/2017 7:46 PM
Competitive Prototyping Wavier ADDM Template v1.0.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Public Law 111 - 23 - Weapon Systems Acquisition Reform Act of 2009 dated 22 MAY 2009
ADDM Application link
Guidance:
Competition Prototype Waiver
BofV
5/18/2017 7:46 PM
Concept Characterization and Technical Description CCTD ADDM Template v 2.1.docx
  
Engineering; Test and EvaluationAir Force; DoDExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Concept Characterization and Technical Description (CCTD) Guide dated 27 OCT 2010
ADDM Application link
Guidance:
The Concept Characterization and Technical Description(CCTD) template summarizes the technical planning and analysis accomplished, and identifies areas of further work needed to mature the concept.  The information within the CCTD represents the analytic basis upon which a material concept was developed, the rationale for decisions made during that development, and the relevant technical documentation that results from early application of Systems Engineering processes and activities.
Template
5/18/2017 7:46 PM
Delegation of Disclosure Authority DDL ADDM Template v 1.2.docx
  
Program ManagementDoDExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: International Programs Security Handbook, Appendix I dated JUN 2009
ADDM Application link
Guidance:
The following Delegation of Disclosure of Authority Letter (DDL) format should be used by the DoD Components to provide disclosure guidance to subordinate commands and agencies and, when applicable, to the DoD contractors.  While all elements identified should be provided in the general order shown, information should be presented in the clearest and easiest-to-use manner.  For example, the usefulness of the DDL for complex systems will be enhanced if items, Authorized for Release and Not Authorize for Release, are broken out by major subsystems and software and disclosures are discussed separately.
Planning for possible foreign involvement should start at the beginning of the weapon system acquisition process and other programs, to facilitate decisions on the disclosure of classified and controlled unclassified information in support of cooperative programs, foreign participation in the DoD procurement activities, and foreign sales. 
The DoD Components shall use the Technology Assessment/Control Plan in DoDD 5530.3 as the basis for making the stated disclosure decisions on weapon system programs.
The DDL is not releasable to Foreign Nationals.
The Delegation of Disclosure Authority Letter (DDL) is issued by the appropriate designated disclosure authority explaining classification levels, categories, scope, and limitations of information under a DoD Component's disclosure jurisdiction that may be disclosed to a foreign recipient. It is used to delegatedisclosure authority to subordinate disclosure authorities.
Template
5/18/2017 7:46 PM
DoD Template for Application of TLCSM and PBL in the Weapon System Life Cycle.pdf
  
Test and EvaluationDefense Logistics Agency; DoDExampleAir Force Examples
The purpose of this template is to provide program managers, their staff, and logistics participants in the acquisition process a tool to assist them in ensuring that effective sustainment is addressed and accomplished over the life cycle. The National Defense Strategy, the Quadrennial Review, and other key defense documents have made it clear that over and above performance we must have weapon systems that have a reduced footprint, reduced cycle times, and are affordable. Meeting these objectives requires early and proactive actions during the acquisition process to address those key logistics criteria and actions that will achieve this goal. This guide provides assistance in that process.
Template
5/18/2017 7:46 PM
Economic Analysis ADDM Template v 1.2.docx
  
Engineering; PurchasingAir Force; DoDExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: AFMAN 65-506 Attachment 5 dated 29 AUG 2011
ADDM Application link
Guidance:
The template below was adapted from AFMAN 65-506.  Refer to Attachment 5 of AFMAN 65-506 for a certification checklist that provides additional guidance for completing the template.
The Economic Analysis template is a systematic approach to selecting the most efficient and cost-effective strategy for satisfying an agency's need. An EA evaluates the relative worth of different technical alternatives, design solutions, and/or acquisition strategies, and provides the means for identifying and documenting the costs and associated benefits of each alternative to determine the most cost-effective solution.Normally associated with Automated Information System (AIS) acquisition programs.
Template
5/18/2017 7:46 PM
Integrated Test Team ITT Charter ADDM Template v 1.1.docx
  
Engineering; Test and EvaluationAir Force; DoDExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: AFI 99-103 dated 16 OCT 2013
ADDM Application link
Guidance:
The Integrated Test Team (ITT) is the overarching test management team that is co-chaired by representatives from the program office and the lead operational test organization.  It is responsible for the T&E grand strategy that supports the program’s acquisition process.  If possible, the ITT must start building the overall Test and Evaluation Master Plan (TEMP) BEFORE the Mildstone (MS) A decision, but certainly no later than immediately after the MS A decision.  If these early phases are bypassed, the ITT must come together as soon as the new program is identified so that key T&E decisions can be made and plans developed.
Follow the guidance in the red, italic font guidance paragraphs to enter descriptions for each section of the ITT Charter in the blue “Click here to enter text” areas.  If a section is not applicable, label it as such and state a short rationale.
Ensure that the Systems Engineering Plan resulting from this template includes all relevant information provided by the reference documents.  Particularly the Acquisition Intelligence Guide, Version 1.0, August 2010.
The Integrated Test Team  (ITT) Charter is a formal, signed document that describes team membership, responsibilities, resources, and the products for which the ITT is responsible.
Template
5/18/2017 7:46 PM
Competitive Prototyping Wavier ADDM Template v1.0 13.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Public Law 111 - 23 - Weapon Systems Acquisition Reform Act of 2009 dated 22 MAY 2009
ADDM Application link
Guidance:
template
5/18/2017 7:46 PM
DoD Anti-Tamper website.aspx
  
DoDReferenceAir Force Examples
The following anti-tamper (AT) reference documents are available via the DoD AT website (https://at.dod.mil), or can be obtained through your DoD Component Office of Primary Responsibility for AT (https://at.dod.mil/content/atea-organization):


AT Plan Template: Provides the outline and guidance to assist with AT work product development,
AT Desk Reference: Provides programmatic guidance on AT Plan deliverables, evaluation points, schedules, and stakeholders,
AT Guidelines: Provides technical guidance on processes and methodologies for determining AT protection level requirements,
AT Security Classification Guide: Provides classification requirements for AT deliverables.


These documents are maintained by the DoD Executive Agent for AT.  The DoD Executive Agent for AT and associated responsibilities are established in DoD Directive 5200.47E, "Anti-Tamper."
 AT is intended to deter, prevent, delay, or react to attempts to compromise critical program information (CPI) (see DoD Instruction 5200.39 for more on CPI) in order to impede adversary countermeasure development, unintended technology transfer, or alteration of a system due to reverse engineering. Properly implemented AT should reduce the likelihood of CPI compromise resulting from reverse engineering attacks for systems that are outside of U.S. control.
5/18/2017 7:46 PM
ADDM SUM April 2017.pdf
  
Contracting; Engineering; Program ManagementAir ForceExampleAir Force Examples
Software user manual for ADDM
gt
5/18/2017 7:46 PM
2366a Certification ADDM Template v 3.0 Edit.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 11/3/2016 ADDM template source review.Based on: Based on: Title 10 U.S.C., Change to Major Defense Acquisition Program Milestone A Requirements Memo, 2366a dated 31 JAN 2016
ADDM Application link
Guidance:
Certification that the program has been approved by the designated individual with overall responsibility for the program to enter into the next phase of the acquisition process.
Reference:




https://af-aqweb.deps.mil/AcqWB_22e0faff-a585-4671-8149-6259dcbb4cdf/AQDocs/2366a.pdf



 
BofV
6/27/2017 12:04 PM
2366b Certification ADDM Template v 3.0 Edit.docx
  
Engineering; Test and EvaluationAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 11/3/2016 ADDM template source review.Based on: Based on: Title 10 U.S.C., Change to Major Defense Acquisition Program Milestone B Requirements Memo,  2366b dated 31 JAN 2016
ADDM Application link
Guidance:
Certification that the program has been approved by the designated individual with overall responsibility for the program to enter into the next phase of the acquisition process.
References:
https://af-aqweb.deps.mil/AcqWB_22e0faff-a585-4671-8149-6259dcbb4cdf/AQDocs/2366b.pdf
 
BofV
6/27/2017 12:05 PM
Test and Evaluation Master Plan TEMP ADDM Template v3.0.docx
  
Cybersecurity; Engineering; Program Management; Test and EvaluationAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016.
ADDM Application link
Guidance:
?This new version ofthe DOT&E TEMP Guidebook complements the January 2015 version of DoD I 5000.02 by illustrating with selective guidance and examples how to develop . and document an adequate test and evaluation (T &E) strategy. The Program Manager will use the TEMP as the primary planning and management tool for all test activities starting at Milestone A.  Best practices outlined in this TEMP Guidebook should be applied to all versions of the TEMP,including the Development Request for Proposal (RFP) TEMP.
The Program Manager will prepare and update the TEMP as needed and to support acquisition milestones or decision points. The TEMP should be specific to the program and tailored to meet program needs. Accordingly, the guidance in this guidebook, in DoDI 5000.02, and in the TEMP format guide are provided to assist in developing the appropriate TEMP format and content for each program. Strict or immediate adherence to the new TEMP format is not required. Use common sense to apply the guidance to fit your program. Evaluation of TEMP adequacy is based on the TEMP's content, not the format.
A TEMP is required by DoDI 5000.02 unless the MDA approves tailored documentation.
Ensure that the narrative in Part I is consistent with the schedule in Part II, the T&E strategy in Part III, and allocated resources in Part IV.  This will require iterative coordination between sub-workgroups and the T&E WIPT
Ensure that the schedule in Part II is consistent with the narrative in Part I, the T&E strategy in Part III, and allocated resources in Part IV.  This will require iterative coordination between sub-workgroups and the T&E WIPT.
Ensure that the T&E strategy in Part III is consistent with the narrative in Part I, the schedule in Part II, and allocated resources in Part IV.  This will require iterative coordination between sub-workgroups and the T&E WIPT.
Ensure that the allocated resources in Part IV is consistent with the narrative in Part I, the schedule in Part II, and the T&E strategy in Part III.  This will require iterative coordination between sub-workgroupsand the T&E WIPT.
---
The Test and Evaluation Master Plan tem????plate d?documents the overall structure and objectives of the Test and Evaluation (T&E) program. It provides a framework within which to generate detailed T&E plans and documents schedule and resource implications associated with the T&E program. The TEMP identifies the necessary Developmental Test and Evaluation (DT&E), Operational Test and Evaluation (OT&E), and Live Fire Test and Evaluation (LFT&E) activities. It relates program schedule, test management strategy and structure, and required resources to: Critical Operational Issues (COIs), Critical Technical Parameters (CTPs), objectives and thresholds documented in the Capability Development Document (CDD), evaluation criteria, and milestone decision points. For Multi-Service or joint programs, a single integrated TEMP is required. Component-unique content requirements, particularly evaluation criteria associated with COIs, can be addressed in a Component-prepared annex to the basic TEMP. See Capstone TEMP).?
 
Template
6/27/2017 2:25 PM
Technology Readiness Assessment TRA ADDM Template v 2.1.docx
  
EngineeringAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.
ADDM Application link
A Technology Readiness Assessment (TRA) is a systematic, metrics-based process that assesses the maturity of, and the risk associated with, critical technologies to be used in Major Defense Acquisition Programs (MDAPs).  A TRA is required for MDAPs at MS B or, if no MS B, a subsequent Milestone.  The TRA is also conducted when otherwise required by the Milestone Decision Authority.  The TRA final report for MDAPs must be submitted to ASD(R&E) for review to support the requirement that ASD(R&E) provide an independent assessment to the MDA.
Within this template, enter applicable verbiage in each of the blue-font “click here to enter text” fields, as specified by the accompanying guidance sections.  If the document section is not applicable, label as such and provide a short rationale.
Template
6/27/2017 2:26 PM
Technology Assessment and Control Plan TA and CP ADDM Template v1.2.docx
  
Engineering; Program ManagementAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.
Technology Assessment/Control Plan (TA/CP) description:  Prior to formal negotiation, the program manager prepares a TA/CP, or similar document, as part of the Program Protection Plan (PPP) for all acquisition programs with international involvement.
ADDM Application link
Guidance:
The policy on Technology Assessment/Control Plan (TA/CP) is in DoD Directive 5530.3.
Prior to formal negotiation, the program manager prepares a TA/CP, or similar document, as part of the Program Protection Plan (PPP) for all acquisition programs with international involvement. The TA/CP is included in the PPP when it is determined that there is likely to be foreign involvement in the development program or when there will be foreign access to the resulting system or related Critical Program Information, by virtue of foreign sales, co-production, follow-on support, exchange program, training, or multinational exercises or operations. Much of the information required for the preparation of the TA/CP can be obtained from the Initial Capabilities Document / Capability Development Document, the Analysis of Alternatives (AoA), the Acquisition Strategy, and the justification and supporting information used in preparing those documents.
Purpose: The Program Manger (PM) uses the Technology Assessment/Control Plan (TA/CP) to do the following:

Assess the feasibility of U.S. participation in joint programs from a foreign disclosure and technical security perspective.
Prepare guidance for negotiating the transfer of classified information and critical technologies involved in international agreements.
Identify security arrangements for international programs.
Provide a basis for the Delegation of Disclosure Authority Letter that contains specific guidance on proposed disclosures.
Support the acquisition decision review process.
Support decisions on foreign sales, co-production, or licensed production, commercial sales of the system, or international cooperative agreements involving U.S. technology or processes.
Support decisions on the extent and timing of foreign involvement in the program, foreign sales, and access to program information by foreign interests.

When it is likely there will be foreign involvement in the program, or foreign access to the resulting system or related information, it is advantageous for the program manager to prepare the TA/CP after completing the identification of CPI and Security Classification Guide (SCG). The TA/CP analysis often assists in developing vulnerabilities and proposed RTP countermeasures. Policies governing the foreign disclosure of intelligence information are in Intelligence Community Directive (ICD) 301 and Director of Central Intelligence Directive (DCID) 6/7*, and nuclear information governed by the Atomic Energy Act. These documents must be consulted when these types of information are involved in an acquisition program.
Template
6/27/2017 2:27 PM
Systems Requirements Document SRD ADDM Template v 1.2.docx
  
Engineering; Test and EvaluationAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on MIL-HDBK-520 dated 19 Dec 2011.
ADDM Application link
The Systems Requirements Document (SRD) translates warfighter Capability Based Requirements into performance based acquisition requirements for a system or subsystem in any program milestone or phase.  This template provides guidance for preparation of the SRD using established Systems Engineering processes.
The System Requirements Document (SRD) template is the primary document driving selection of a realistic and affordable solution to the warfighter’s Capability Based Requirements (CBRs).
Template
6/27/2017 2:28 PM
Systems Engineering Plan SEP ADDM Template v 2.2.docx
  
Contracting; Engineering; Program Management; Requirements Management; Test and EvaluationAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review. Based on: System Engineering Plan Outline dated 20 Apr 2011
ADDM Application link
Guidance:
The purpose of the Systems Engineering Plan (SEP) is to help programs develop their Systems Engineering (SE) approach, providing a firm and well-documented technical foundation for the program. The SEP is a living document in which periodic updates capture the program’s current status and evolving SE implementation and its relationship with the overall program management effort.
Enter applicable verbiage in each of the blue-font “click here to enter text” fields, as specified by the accompanying guidance sections.  If the document section is not applicable, label as such and provide a short rationale.
Ensure that the Systems Engineering Plan resulting from this template includes all relevant information provided by the reference documents.  Particularly the Acquisition Intelligence Guide, Version 1.0, August 2010.
 “All links in this document were accurate at the time of writing. Due to web site security measures, though, clicking on some links from this document may give the error message "A Security Problem has Occurred" for a given URL, or a “Page Not Found” message. If you receive these errors, copy and paste the URL into your browser's address bar to establish the link.”
---
The System Engineering Plan template is a description of the program's overall technical approach including processes, resources, metrics, applicable performance incentives, and the timing, conduct, and success criteria of technical reviews.
 
Template
6/27/2017 2:29 PM
System Threat Assessment Report STAR ADDM Template DRAFT v 2.1.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review. Based on: DAG dated 05 May 2013
ADDM Application link
Guidance:
The STAR will be prepared by DoD components as required by; DoDD 5000.01, “Defense Acquisition,” 20 November 2007, DoD Instruction 5000.2, “Operation of the Defense Acquisition System,” 8 December 2008.  For the Air Force the STAR is prepared by the National Air and Space Intelligence Center (NASIC).
The STAR is the authoritative, system-specific threat capabilities reference for Acquisition Category (ACAT) I programs and Space Major Defense Acquisition Programs (MDAP).  This document includes a system-specific overview of threat system capabilities that could be employed against a proposed U.S. system and the projected threat environment in which the U.S. system will operate at IOC (or an established baseline) and IOC/baseline +10 years.  As a minimum, the STAR should include threat capabilities of those countries addressed in the Multi-Service Force Deployment (MSFD) scenarios.  The STAR is typically required by MS B or KDP B and is updated as necessary every 18 months throughout the development of the system.
-----
The STAR is the authoritative, system-specific threat capabilities reference for Acquisition Category (ACAT) I programs and Space Major Defense Acquisition Programs (MDAP).  It is developed by NASIC and either (1) validated by DIA for ACAT ID and Space MDAP programs or (2) approved by NASIC/CC for ACAT IC programs.
 
Template
6/27/2017 2:29 PM
Security Classification Guide ADDM Template v 2.1.docx
  
Air ForceExampleAir Force Examples
The Security Classification Guide:
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: DODM 5200.45 dated 02 Apr 2013
ADDM Application link
Guidance:
a. Classification management procedures call for the timely issuance of comprehensive guidance regarding classification of information concerning any system, plan, program, project, or mission under the jurisdiction of the OCA, the unauthorized disclosure of which reasonably could be expected to cause damage to national security. Precise classification guidance is prerequisite to effective and efficient information security and assures that security resources are expended to protect only that which truly warrants protection in the interests of national security. Reference (d) and its implementing guidance, Reference (e), provide general requirements and standards concerning the issuance of security classification guides while Reference (f) provides DoD guidance on development, promulgation, distribution, maintenance, and cancellation of security classification guides.
b. Information is classified, in accordance with guidance in References (d), (e), and (f), to provide an appropriate level of protection. Therefore, it is essential that a classification guide identify the specific items of information and the levels of protection required, as well as the time periods for which protection must be provided.
c. A classification guide will be issued as early as practical in the life cycle of the classified system, plan, program, project, or mission. The requirements of Reference (f) regarding classification, declassification, downgrading, marking, and security classification guides should be reviewed and understood in preparation for writing a security classification guide.
d. DoD information that does not, individually or in compilation, require classification, must still be reviewed in accordance with DoDD 5230.09 (Reference (i)), prior to any release to the public. In addition, such information must also be reviewed for compliance with the provisions of DoDI 8550.01 (Reference (j)), prior to its placement on any publicly accessible Internet site. Information that does not require classification may nevertheless be exempt from release to the public or have other restrictions applied when released to other U.S. Government agencies
(e) Scientific, technological, or economic matters relating to the national security (subsection 1.4(e));
(f) U.S. Government programs for safeguarding nuclear materials or facilities (subsection 1.4(f));
(g) Vulnerabilities or capabilities of systems, installations, infrastructures, projects, plans, or protection services relating to the national security (subsection 1.4(g)); or
(h) The development, production, or use of weapons of mass destruction (subsection 1.4(h)).
The recommended cover page format for a security classification guide includes all of the information shown above. If necessary, use an acronym, short title or project number in order to keep title unclassified; place the most significant words of the guide’s title first. Mark it “FOR OFFICIAL USE ONLY” or, if classified, with the appropriate classification markings (including classification authority block, portion marks, and any special handling caveats and distribution controls).
Template
6/27/2017 2:32 PM
Risk Management Plan ADDM Template v 1.1.docx
  
Air ForceExampleAir Force Examples; PM Acquisition Management; Program Execution
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on AFLCMC\EN dated 01 DEC 2015
ADDM Application link
Guidance:
(Extracted from The 2015 DoD Risk, Issue, and Opportunity (RIO) Management Guide for Defense Acquisition Programs, AFI 63-101, and AFPAM 63-128.)

AFI 63-101 states that “PMs shall pursue a comprehensive integrated risk analysis throughout the life cycle and shall prepare and maintain a risk management plan [RMP]."  Risks include, but are not limited to, cost, schedule, performance, technical, product data access, technology protection, integration, and Environment, Safety, and Occupational Health (ESOH) risks. The PM has primary responsibility for risk management and the RMP; the program's Lead Systems Engineer (LSE) / Chief Engineer (CE) takes direction from the PM and ensures that technical risks are incorporated into both the program’s overall risk management effort and its life-cycle systems engineering (SE) strategy.
The DoD RIO Management Guide states that "The practice of risk management draws from many disciplines, including program management, systems engineering, requirements definition, earned value management (EVM), production planning, quality assurance, and logistics. Programs should strive to follow sound risk management processes as outlined; however, the Department recognizes some tailoring will be required as programs adapt to fit within program-specific circumstances."  Industry also plays a central role in executing the management necessary for delivery of acquisition products, so a close collaboration between government and industry is an essential ingredient of productive and economic risk, issue and opportunity management.
Because of the requirements and expectations described above, this RMP template is primarily designed to describe the types of information and considerations that a plan, tailored to a specific program of record, might contain. While the template is most applicable to an ACAT I or II program, ACAT III programs can also use it as a guide to write a more tailored plan to meet their program needs. Additionally, while not currently required, System Program Managers (SPMs) and related system maintenance / sustainment organizations may also benefit from using this template as part of a formal risk management program for their production operations (aside from what they may already be doing as part of safety/occupational risk governed by AFI 90-802, AFI 91-202 and MIL-STD-882).
The Air Force has provided direction in AFI 63-101, and non-directive guidance in AFPAM 63-128, to define the steps of the life cycle risk management (LCRM) process.  AFPAM 63-128 also provides examples and considerations for risk management throughout the life cycle of a program, describing a standardized 5x5 risk reporting matrix, risk likelihood ranges, consequence rating criteria, and the role that risk management plays at each milestone.  See AFI 63-101 Chapter 4 and AFPAM 63-128 Chapter 12 for more details.



Regardless of the particular RMP format, the Risk Management Plan should:


Explain how the program manages risks to achieve cost, schedule and performance goals.
Document an organized, comprehensive and integrated approach for managing risks.
Define the goals, objectives, and the program office’s risk management processes.
Define an approach to identify, analyze, handle and monitor risks across the program.
Document the process to request and allocate resources (personnel, schedule, and budget) to handle risks.
Define the means to monitor the effectiveness of the risk management process.
Document the integrated risk management processes as they apply to contractors, subcontractors and teammates.


The RMP can be incorporated into the Acquisition Strategy (AS) or other appropriate planning document.  The RMP shall be linked to the risk management activities described in other planning documents (e.g., Source Selection Plan, Life Cycle Sustainment Plan [LCSP], Systems Engineering Plan [SEP], Programmatic Environmental, Safety and Occupational Health Evaluation [PESHE]). 
 
Template
6/27/2017 2:34 PM
Replaced System Sustainment Plan ADDM Template v 1.1.docx
  
Air ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Title 10, USC, Section § 2437
ADDM Application link
Guidance:
Title 10, USC, Section § 2437 requires that the DoD Component sponsoring an MDAP that will replace an existing system shall prepare a Replaced System Sustainment Plan for the existing system if the capability provided by the existing system will remain necessary and relevant during fielding of and transition to the new system.  The plan shall provide for an appropriate level of budgeting for sustaining the existing system until the replacement system to be developed under the major defense acquisition program is fielded and assumes the majority of responsibility for the mission of the existing system.
----
The Replaced System Sustainment Plan template describes how to sustain the existing system until the replacement system to be developed under the major defense acquisition program is fielded and assumes the majority of responsibility for the mission of the existing system.
Template
6/27/2017 2:35 PM
Program Protection Plan PPP ADDM Template v3.2.docx
  
Program ManagementAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Program Protection Plan Outline and Guidance dated JUL 2011
ADDM Application link
Guidance:
This document provides an outline, content, and formatting guidance for the Program Protection Plan (PPP) required by DoDI 5000.02 and DoDI 5200.39. The outline structure and tables are considered minimum content that may be tailored to meet individual program needs.
General Guidance:

Program Protection is the integrating process for managing risks to advanced technology and mission-critical system functionality from foreign collection, design vulnerability or supply chain exploit/insertion, and battlefield loss throughout the acquisition lifecycle.
The purpose of the PPP is to help programs ensure that they adequately protect their technology, components, and information. This includes information that alone might not be damaging and might be unclassified, but that in combination with other information could allow an adversary to clone, counter, or defeat warfighting capability.
The process of preparing a PPP is intended to help program offices consciously think through what needs to be protected and to develop a plan to provide that protection.
Once a PPP is in place, it should guide program office security measures and be updated as threats and vulnerabilities change or are better understood. It is important that an end-to-end system view be taken when developing and executing the PPP. External, interdependent, or government furnished components that may be outside a program managers' control must be considered.
The PPP should be a useable reference within the program for understanding and managing the full spectrum of program and system security activities throughout the acquisition lifecycle. The PPP is a plan, not a treatise; it should contain the information someone working on the program needs to carry out his or her Program Protection responsibilities and it should be generated as part of the program planning process.
At Milestone A, it’s possible that not all Program Protection information will be available. Complete the tables/sections with the information that is available and document the plan to update this information as more details become available. At minimum, a Milestone A PPP should include an initial criticality analysis, candidate CPI, potential countermeasures, and the Information Assurance Strategy. The Milestone B PPP should be a comprehensive document.
The Acquisition Information Assurance (IA) Strategy must now be appended to the PPP. Some sections (e.g. IA threats, MAC level)) have been moved to the body of the PPP for document streamlining. Other sections (e.g. Program Information, schedule) may be included in the Acquisition IA Strategy or referenced when other documents contain that information (e.g. Acquisition Strategy). The information must be available but does not need to be repeated in multiple documents if it is accessible to users of the PPP.
If a topic/section can be sufficiently covered in a sentence instead of a paragraph, write a sentence.
Wherever possible, reference or point to other documents containing relevant information rather than duplicating the information in the PPP unless that information would be valuable to users of the plan. Do not simply repeat general policies unless that information would be valuable to the user of the plan.
Appendices are required where relevant and appropriate. For example, every acquisition program must have an Information Assurance Strategy but not all acquisition programs will have an Anti-Tamper plan.
Classification Guidance: The PPP should be classified by content. Threat and vulnerability information is commonly classified at SECRET or above. Detailed descriptions of CPI and critical functions/components may also be classified. The program Original Classification Authority is responsible for determining appropriate classification of the PPP and related information. The program may opt to reference some tables (e.g. threats, vulnerabilities) as classified appendices.

The office of primary responsibility for this guide is the Deputy Assistant Secretary of Defense for Systems Engineering (DASD(SE)). This office will continue to develop and coordinate updates to the guide as required, based on any future policy changes and customer feedback. To provide feedback, send e-mail to dasd-se@osd.mil.
-----
The Program Protection Plan (PPP) is a comprehensive plan to safeguard critical program and technology information that is associated with a defense acquisition program. The level of detail and complexity of the PPP will vary based on the criticality of the program or system, the CPI, and the phase of the acquisition process being addressed. The PPP lays out the scheme to protect the program during the period from program initiation until the system is fielded (initial operational capability [IOC]), and through any modification or product improvement that requires protection from compromise.
ADDM Application link
Template
6/27/2017 2:36 PM
Post Implementation Review ADDM Template v 1.1.docx
  
Test and EvaluationAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Defense Acquisition Guidebook dated 15 MAY 2013
ADDM Application link
Use the template below to create the Post Implementation Review Plan (PIR).  The PIR is not a single event or test. It is a sequence of activities that when combined provide the necessary information to successfully compare actual system performance to program expectations. In some cases, these activities can take place over a long period of time. The final PIR Plan is due at the FRF/FD Decision Review.
The PIR should take place post-IOC after a relatively stable operating environment has been established and the data identified in the PIR plan has been collected.  Time frame for the PIR varies with the solution deployment strategy, but the PIR is to be executed and a report submitted prior to Full Operational Capability.  If an FOC is not planned, the PIR is to be executed within one year of the IOC.
Routing of the draft and final PIR Plan should include the identified stakeholders. An information copy of the final PIR Plan and Report is sent to the Senior Military Advisor DOT&E and the Program's CAPE Action Officer.
The Post Implementation Review Plan is an assessment and review of the completed working solution. It will be performed after a period of live running, some time after the project is completed.
 
Template
6/27/2017 2:38 PM
Life Cycle Sustainment Plan LCSP Outline AFLCMC ADDM Template v2.docx
  
Life Cycle LogisticsAir ForceExampleAir Force Examples
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: Air Force Life Cycle Management Center Standard Process for Life Cycle Sustainment Plans (LCSP) dated 16 JUL 2016
ADDM Application link
1.0    The Life Cycle Sustainment Plan (LCSP) documents the Program Manager and Product Support Manager's plan for formulating, implementing and executing the sustainment strategy, and is part of the overall Acquisition Strategy of a program. It details the system’s sustainment Key Performance Parameters (KPPs)/Key System Attributes (KSAs). The LCSP describes the approach and resources necessary to develop and integrate sustainment requirements into the system's design, development, testing, deployment and sustainment phases while controlling overall program Total Ownership Costs (TOC).  It should include sufficient detail for a program to execute against, to include a product support integrated master schedule. 
1.1     The LCSP shall be integrated across the system life cycle including strategy development, planning, development, production, fielding, modification (which may include technology advancement), support, and disposal. The LCSP streamlines, consolidates, and makes visible to leadership all product support aspects of the program.
1.2     The LCSP evolves into an execution plan to describe the manner in which life cycle sustainment requirements are acquired, applied, managed, assessed, measured, and reported after system fielding.  By Milestone (MS) C, the LCSP should detail how the program will meet readiness targets, sustain system performance capability threshold criteria, comply with Title 10 United States Code (USC) 2464, Core Logistics Capabilities, and 10 USC 2466, Limitations on the Performance of Depot-level Maintenance of Materiel, mitigate operations and support (O&S) costs, reduce the logistics footprint and comply with environmental and other logistics related regulations. When the program enters the O&S Phase, the LCSP is the execution plan for sustaining the system to include disposal. The LCSP should be used to support and align efforts to the program’s planning, programming, budgeting, and execution activities.
1.3     This process applies to all acquisition programs as defined in AFI63-101/20-101, Integrated Life Cycle Management, paragraph.
Template
6/27/2017 2:40 PM
Live Fire T E Wavier ADDM Template v1.0.docx
  
Program Management; Test and EvaluationAir ForceExampleAir Force Examples; PM Technical Management; Test and Evaluation Mgmt
A new template was created based on LFT&E statute,  Title 10 U.S.C § 2366, which requires a LFT&E program to include Full Up System Level (FUSL) testing unless a waiver from FUSL is granted with a certification by the Under Secretary of Defense for Acquisition, Technology and Logistics (USD(AT&L)) or the DoD component acquisition executive (CAE) that FUSL testing would be unreasonably expensive and impractical. 
Template
6/27/2017 2:42 PM
Post CDR Report ADDM Template v 2.0.docx
  
EngineeringAir ForceExampleAir Force Examples; PM Technical Management; Engineering Management
This Template is courtesy of the Air Force, provided from the Air Force Acquisition Document Development & Management (ADDM) System, which is a restricted DoD site. Please note that this is an Air Force Template provided for your guidance, and that the other services or agencies may have different documentation requirements.
This document is current as of 3/9/2016 ADDM template source review.Based on: DoDI 5000.02 dated 07 JAN 2015
ADDM Application link
Guidance:
Per the Memorandum for Secretaries of the Military Departments Directors of the Defense Agencies, dated 24 February 2011, the Program Manaager’s reporting responsibility for the Post-Critical Design Review (CDR) Report currently required by DoD Instruction 5000.02, Enclosure 2, para 6.c(6)(c)(1) has been eliminated.  The Office of the Deputy Assistant Secretary of Defense (Systems Engineering) (DASD(SE)) will participate in program CDRs and prepare a brief assessment of the program’s design maturity and technical risks which may require Milestone Decision Authority (MDA) attention.
The system-level Critical Design Review (CDR) provides an opportunity to assess design maturity.  For complex systems, the program manager may conduct a CDR for each subsystem or configuration item. These individual reviews would lead to an overall system CDR. When individual reviews have been conducted, the emphasis of the overall system CDR should focus on configuration item functional and physical interface design, as well as overall system detail design requirements. The CDR determines whether the hardware, human, and software final detail designs are complete, and whether the Integrated Product Team is prepared to start system fabrication, demonstration, and test.
The subsystem detailed designs are evaluated to determine whether they correctly and completely implement all system requirements allocated to the subsystem, and whether the traceability of final subsystem requirements to final system detail design is maintained. At this review, the Integrated Product Team also reviews the results of peer reviews on requirements and final detail design documentation, and ensures that the latest estimates of cost (development, production, and support) are consistent with the detail design. A successful review is predicated on the Integrated Product Team's determination that the subsystem requirements, subsystem detail design, results of peer reviews, and plans for testing form a satisfactory basis for proceeding into system fabrication, demonstration and test.
The Post-CDR Assessment provides an opportunity to assess design maturity prior to establishment of the product baseline. (Reference: DoDI 5000.02, paragraphs 6.c(6)b and 6.c(6)c.
Template
6/27/2017 2:45 PM
1 - 30Next