| 1.2.1.1-1-1 Ensure Initial Capabilities Document is adequate and complete |
Phase 0 |
|
Ensure the Initial Capabilities Document documents the need for a materiel approach to a specific capability gap derived from an initial analysis of materiel approaches executed by the operational user and, as required, an independent analysis of materiel alternatives. It defines the capability gap in terms of the functional area, the relevant range of military operations, desired effects and time. Ensure the ICD summarizes the results of the Doctrine, Organization, Training, Material, Leadership and Education, Personnel, and Facilities (DOTMLPF) analysis and describes why nonmaterial changes alone have been judged inadequate in fully providing the capability. (CJCSI 3170 G). Ensure the Net-Ready Key Performance Parameter (NR-KPP) is defined in the ICD, consists of testable characteristics, and contains appropriate performance measures. Ensure measurable and testable criteria for how the system supports military operations, is entered and managed on the network and how effectively it exchanges information is specified with threshold and objective values IAW the Joint Capabilities Integration and Development System (JCIDS) Net-Ready KPP requirement. Cyber resiliency must be addressed through the JCIDS Survivability KPP. (Note: ORD, Mission Area Needs/Analysis documents are obsolete, replaced by the ICD for new acquisitions). Ensure the following addressed: Mission Area Assessment (MAA), Mission Needs Analysis (MNA), Mission Needs Statement (MNS).
|
SFWC 3.3, SFWC 3.4, SFWC 3.5; AFMAN 63-119 A4.7.1; AFMAN 63-119 A4.7.2; AFMAN 63-119 A9.1
|
Initial Capabilities Document (ICD)
|
AFMAN 63-119 or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis and Validation Chapter
|
| 1.2.1.1-1-2 Ensure Initial Capabilities Document is approved by Joint Requirements Oversight Council or equivalent organization |
Phase 0 |
|
Ensure a copy of the Joint Requirements Oversight Council (JROC) or equivalent organization memo approving the document from the Customer Requirements Lead for the program is obtained. Ensure requirements include inputs from all stakeholders and concepts of operations.
|
SFWC 3.3, SFWC 3.4, SFWC 3.5; AFMAN 63-119 A4.2
|
Initial Capabilities Document (ICD)
|
AFI 63-101 or equivalent; AFMAN 63-119 or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis and Validation Chapter
|
| 1.2.1.1-1-3 Ensure Capability Development Document is adequate and complete |
Phase 0 |
Phase A |
|
Ensure the Capability Development Document (CDD) builds on the Initial Capabilities Document and provides the detailed operational performance parameters necessary to complete design of the proposed system. Ensure Analysis of Alternatives (AoA) complete prior to defining the Initial Capabilities Document in creating Key Performance Parameters. Ensure Measures of Effectiveness (MOEs) reflect operational utility, are quantifiable and measurable, and are derived from the capability documents. Ensure formal VV&A (validation, verification and accreditation) has occurred for each model chosen. Ensure coordination and approval at appropriate levels prior to each milestone, after major program changes, and sufficiently early to develop the OT&E test concept and plan. Ensure critical performance parameters are developed and documented. Ensure preliminary system/mission requirements are aligned to the applicable user requirements document. Ensure all assumptions and constraints are identified and supported by relevant requirements documents and requirements verification mapped back to the system's capabilities documents. Ensure modification programs that introduce new capability include a Table of Performance Parameters/Attributes (KPP, KSA, other or attributes) with minimum Threshold/Objective values similar to the format for a CDD/CPD. Ensure sustainment modifications identify CDD/CPD requirements the modification is intended to sustain. Ensure documentation states the appropriate cybersecurity impact values (High, Moderate, and Low) for Confidentiality, Integrity and Availability as well as listing the appropriate security overlays.
|
SFWC 3.6, SFWC 3.9, SFWC 3.10, SFWC 3.11, SFWC 3.12; AFMAN 63-119 A3.2.2; AFMAN 63-119 A3.3; AFMAN 63-119 A4.1; AFMAN 63-119 A4.1.1; AFMAN 63-119 A4.1.2; AFMAN 63-119 A4.14
|
Capability Development Document (CDD)
|
Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Design Assurance Chapter; AFMAN 63-119 or equivalent
|
| 1.2.1.1-1-4 Ensure enabling concept (EC) document is complete and approved |
Phase 0 |
|
Ensure Review of Capabilities-Based Assessment (CBA), Capabilities-Based Planning (CBP), and Integrated Planning Process (IPP) reports. Review existing Enabling Concepts (ECs) for relevance. Ensure Architecture Products for EC. Ensure existing EC documented and current. Ensure Enabling Concept (EC) delivered. Ensure existence of Initial Capabilities Document (ICD)/Doctrine Organization Training Materiel Leadership and Education Personnel Facilities (DOTMLPF) Change Recommendation.
|
NA
|
Enabling Concept Documents
|
AFI 63-101 or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Design Assurance Chapter
|
| 1.2.1.1-1-5 Ensure program requirements trace to capabilities-based assessment is performed |
Phase 0 |
|
Ensure Functional Area Analysis, Functional Needs Analysis, and Functional Solutions Analysis are part of the Integrated Planning Process (IPP). Ensure Prototypes developed. Ensure initial capabilities document or equivalent requirement document exists.
|
NA
|
Capability Development Document (CDD); Integrated Planning Process (IPP) Products
|
AFI 63-101, Acquisition and Sustainment Life Cycle Management, 8 April 2009 or equivalent
|
| 1.2.1.1-1-6 Ensure the Capabilities Based Requirements Document is flowed down through the Analysis of Alternatives, acquisition strategy and Test and Evaluation Master Plan |
Phase 0 |
|
Ensure the Capabilities Based Requirements Document (CBRD) is flowed to the operational test concepts and Operational Test and Evaluation Plan. Ensure changes to the CBRD are flowed through concepts and captured in related documents. Ensure the requirements strategy and acquisition strategy are fully supported.
|
AFMAN 63-119 A4.3; AFMAN 63-119 A7.2; AFMAN 63-119 A7.2.1; AFMAN 63-119 A22.1.2
|
NA
|
AFMAN 63-119 or equivalent; Mission Assurance Guide, TOR-2007(8546)-6018, Rev B, Requirements Analysis and Validation Chapter
|