Can you please provide me with, or point me to someone who can assist with providing the below USN ACAT III document templates?
Acquisition Decision Memorandum (ADM)
Acquisition Program Baseline (APB)
Analysis of Alternatives (AoA) Study Guide
Bandwidth Requirements Review (BRR)
Clinger-Cohen Act (CCA) Compliance
Concept of Operations (CONOPS)
Core Logistics Determination/Core Logistics and Sustaining Workloads Est.
DoD Component Cost Estimate
DoD Component Live Fire Test and Evaluation (LFT&E) Report
DOT&E Report on Initial Test and Evaluation (IOT&E)
Frequency Allocation Application (DD Form 1494)
Information Support Plan (ISP)
Information Technology and National Security Interoperability Certification
Item Unique Identification (IUID) Implementation Plan
Life-Cycle Mission Data Plan (LMDP)
Already have the LCSP
Live-Fire Test and Evaluation Report
Low-Rate Initial Production (LRIP) Quantity
Operational Test Agency (OTA) Report on OT&E Results
Operational Test Plan--S" before start of OT&E (R for non-DOT&E oversight)
PESHE and NEPA/E.O. 12114 Compliance Schedule
Program Protection Plan
Spectrum Supportability Risk Assessment/ Determination
Systems Engineering Plan (SEP)
Technology Targeting Risk Assessment
Test and Evaluation Master Plan (TEMP)
Validation On-line Life-cycle Threat (VOLT)
Waveform Assessment Application
The templates and/or explanation of required information are contained below or at the reference noted. Given the extensive request, it is recommended that courses in the PM and Systems Engineering curriculum be taken as this is covered in them.
Acquisition Decision Memorandum (ADM) – The Acquisition Decision Memorandum (ADM) documents the decisions made by the Milestone Decision Authority (MDA) during a Milestone Decision Review. The MDA makes all final acquisition program decisions. The ADM (signed by the MDA) outlines the formal justification that allows a program to proceed into the next acquisition phase. The ADM also lists the tasks to be completed during an acquisition phase and the responsible agent for those tasks. Exit Criteria are also listed in the ADM.
Acquisition Program Baseline (APB) – https://www.dau.edu/cop/pbl/_layouts/15/WopiFrame.aspx?sourcedoc=/cop/pbl/Lists/Tools/Attachments/1/DFAS%20APB%20Template.pdf&action=default
***Affordability Analysis – Affordability Analysis is a tool that DoD Components use to determine their priorities and what they can and what they can’t afford on their program(s). It’s based upon the Life-Cycle Cost (LCC) for current or future program(s). The purpose of the analysis is to avoid starting or continuing programs that cannot be produced and supported within reasonable expectations for future budgets. The Milestone Decision Authority (MDA) approves the Affordability Analysis at the following milestones:
- Prior to the Materiel Development Decision (MDD): the analysis will yield tentative cost goals and inventory goals
- Milestone A: the analysis will yield affordability goals
- Development RFP Release Decision Point: the analysis will yield binding affordability caps
- Milestone B and beyond: the analysis will yield binding affordability caps
Analysis of Alternatives (AoA) Study Guide – see DAG Chapter 2-2.3 -- Course recommendation: CLR 151 Analysis of Alternatives. This on-line course provides professionals who lead or directly support AoAs with a comprehensive introduction to conducting AoA activities. Sponsors use the AoA to assess and prioritize potential materiel solutions and trade space in support of validated military capability requirements.
Bandwidth Requirements Review (BRR) – 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 Net-Ready Key Performance Parameter (NR-KPP) guidance in Appendix E to Enclosure D of the Manual for the Operation of the Joint Capabilities Integration and Development System (JCIDS) (Reference (r)) and Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 5123.01G (Reference (s)).
Clinger-Cohen Act (CCA) Compliance – see DAG Chapter 6–3.6.8.
Concept of Operations (CONOPS) – Determined by warfighter community. See JCIDS Manual
Core Logistics Determination/ and Sustaining Workloads Est. – see DAG Chapter 4–18.104.22.168.1
Core logistics capability (See US Code Title 10, 2464) is required to ensure a stable source of technical competence to ensure effective and timely response to mobilization, national defense contingency situations, or other emergency requirements. Programs undergo a core determination process to evaluate whether the statutory requirements apply and informs the program’s 2366a certification submission.
CYBERSAFE Certification– see DAG Chapter 6–3.10; DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology (IT), March 12, 2014
Cybersecurity Strategy – see DAG Chapter 6–3.10
DoD Component Cost Estimate – see DAG Chapter 2-3.3
Course recommendation: BCF 130 Fundamentals of Cost Analysis. In this course professionals are introduced to policies and techniques used in cost analysis including DoD cost analysis, definition and planning of a cost estimate, data collection and their sources, data normalization, life cycle data analysis, risk and uncertainty, documentation requirements and budgeting considerations.
DoD Component Live Fire Test and Evaluation (LFT&E) Report – see DAG Chapter 8-3.2.5
DOT&E Report on Initial Test and Evaluation (IOT&E) – see DAG Chapter 8–2.2.2
DOT&E approves all OT&E plans for all programs on the DOT&E Oversight List, including, but not limited to, early operational assessments (EOAs), operational assessments (OAs), Limited User Tests (LUTs), IOT&E, and Follow-on Operational Test & Evaluation (FOT&E).
Exit Criteria – As determined by the Milestone Decision Authority (MDA).
Frequency Allocation Application (DD Form 1494) – see DAG Chapter 3-4.3.20
The DD-1494, Application for Equipment Frequency Allocation, has four stages, which reflect the increasing maturity of available spectrum information during development. The DD-1494 form is submitted to National Telecommunications and Information Administration (NTIA) for approval of spectrum allocation, without which emitters cannot operate within CONUS, and to the International Telecommunications Union (ITU) for satellites. The NTIA Manual of Regulations and Procedures for Federal Radio Frequency Management (Redbook) chapter 3 addresses international treaty aspects of the spectrum, and chapter 4 addresses frequency allocations.
Information Support Plan (ISP) – see Interoperability of Information Technology (IT), DoDI 8330.01,
PMs must develop the ISP online by entering system information through the GTG-F portal (https://gtg.csd.disa.mil).
The ISP is a key document in achieving interoperability certification. The ISP describes IT and information needs, dependencies, and interfaces for programs. It focuses on the efficient and effective exchange of information that, if not properly managed, could limit or restrict the operation of the program in accordance with its defined capability.
Information Technology and National Security Interoperability Certification – see Interoperability of Information Technology (IT), DoDI 8330.01,
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.
Item Unique Identification (IUID) Implementation Plan – see DAG Chapter 6–3.7.4
Life-Cycle Mission Data Plan (LMDP) – see DAG Chapter 7–5.1.3
Several tools assist PMs in managing impacts from adversary threats. They include the Lifecycle Mission Data Plans (LMDPs).
The LMDP is the PM’s plan that articulates how the program and other organizations intend to address specific program needs for intelligence data required to operate mission systems. Typical types of data dependencies are: Characteristics and Performance (C&P) or Order of Battle data that enable prioritization and defense against enemy systems; Signatures data that enable you to detect and distinguish between friendly, neutral and enemy systems; Geospatial Intelligence (GEOINT) that provide
you mapping and locating data; Electronic Warfare Integrated Reprogramming (EWIR) data that identifies and counteracts enemy radar and detection. Gaps in data diminish the capabilities of systems and can render them vulnerable to enemy actions.
***Already have the LCSP
Live-Fire Test and Evaluation Report – see DAG Chapter 8-3.2.5
Low-Rate Initial Production (LRIP) Quantity – see DAG Chapter 8-2.2.2
In accordance with 10 USC 139, the D,OT&E approves the number of low-rate initial production (LRIP) systems required for adequate operational testing of programs on the DOT&E Oversight List. For programs not on DOT&E oversight for operational testing, the Service OTA determines the number of LRIP systems required for OT&E. DOT&E and the OTAs routinely engage the PM in those decisions. For programs not on the DOT&E Oversight List, the Service or Defense Agency OTA works with the PMs for OT&E, including planning, applicable oversight, and execution and reporting; in accordance with DoDI 5000.02 (Encl. 5, para 3(a) – page 70).
Operational Test Agency (OTA) Report on OT&E Results – see DAG Chapter 8-22.214.171.124
In accordance with DoDI 5000.02 , the OTA provides an OTA Report of OT&E results, based on OT conducted to date, in support of the Milestone C Decision. The OTA Report focuses on:
-Progress toward operational effectiveness, operational suitability, and survivability (including cybersecurity) or lethality.
- Significant trends noted in development efforts.
- Programmatic voids.
- Risk areas.
- Adequacy of requirements.
- The ability of the program to support adequate operational testing.
Operational Test Plans – see DAG Chapter 8-126.96.36.199
The OTP documents adequate testing to assess whether the system under test is operationally effective and operationally suitable when used by representative, properly trained personnel in an operationally realistic environment. In the case of OA, the OTP documents testing that supports progress towards the assessment of operational effectiveness, operational suitability, and survivability (including cybersecurity) or lethality.
PESHE and NEPA/E.O. 12114 Compliance Schedule see DAG Chapter 3–4.3.9
At Milestone B, the Systems Engineer and their ESOH SMEs document the results of their TMRR ESOH activities in the Programmatic ESOH Evaluation (PESHE) and their NEPA/EO 12114 Compliance Schedule. The PESHE consists of the ESOH hazard data, hazardous materials management data and any additional ESOH compliance information required to support analyses at test, training, fielding and disposal sites.
Program Protection Plan – see DAG Chapter 6–3.10.2 (IT Systems)
Should-Cost Target – see DAG Chapter 1–188.8.131.52
Spectrum Supportability Risk Assessment/Determination – see DAG Chapter 3-4.3.20
The SSRA is used within the DoD as the basis for assessing the feasibility of building and fielding equipment that operate within assigned frequency bands and identifying potential de-confliction situations. The DD-1494, Application for Equipment Frequency Allocation, has four stages, which reflect the increasing maturity of available spectrum information during development. The DD-1494 form is submitted to National Telecommunications and Information Administration (NTIA) for approval of spectrum allocation, without which emitters cannot operate within CONUS, and to the International Telecommunications Union (ITU) for satellites.
Systems Engineering Plan (SEP) – see DAG Chapter 3-2.2
SE planning, as documented in the Systems Engineering Plan (SEP), identifies the most effective and efficient path to deliver a capability, from identifying user needs and concepts through delivery and sustainment. SE event-driven technical reviews and audits assess program maturity and determine the status of the technical risks associated with cost, schedule and performance goals.
Technology Targeting Risk Assessment – see DAG Chapter 7-5.1.4
Several tools assist PMs in managing impacts from adversary threats. They include the Technology Targeting Risk Assessments (TTRAs).
The TTRA is a country-by-country assessment conducted by the DoD entities within the DISE that quantify risks to critical program information (CPI) and related enabling technologies for weapons systems, and advanced technologies or programs; facilities such as laboratories, factories, research and development sites (e.g., test ranges); and military installations.
Test and Evaluation Master Plan (TEMP) – see DAG Chapter 8-2.7
The TEMP includes a strategy for T&E and begins with a review and understanding of the threat and the requirements. The purpose of a T&E program is to characterize system capabilities across the intended operational conditions, verify that testable requirements are met or not met, and inform decision-makers. Program managers devise a T&E strategy generating the knowledge necessary for the acquisition, programmatic, operational, technical, and life-cycle support decisions of a program.
Validation On-line Life-cycle Threat (VOLT) – see DAG Chapter 7-5.1.1
Several tools assist PMs in managing impacts from adversary threats. They include the Validated On-line Life-cycle Threat (VOLT) Reports.
While VOLT reports support Acquisition Category (ACAT) I-III programs, only Major Defense Acquisition Programs, Major Automated Information System programs, and programs on the Director, Operational Test and Evaluation (DOT&E) Oversight List require a unique, system-specific VOLT report to support capability development.
Exemplars of VOLT reports are available at the following Secure Internet Protocol Router Network (SIPRNet) site: https://intellipedia.intelink.sgov.gov/wiki/Validated_Online_Lifecycle_Threat_Reports
Waveform Assessment Application– See DoDI 4630.09