Welcome to the Requirements Document Wizard (RDW)!

You are working on an Information Systems Capabilities Development Document (IS-CDD) relevant to the 2021 version of the Joint Capabilities Development and Integration System (JCIDS) Manual.

The purpose of the IS-CDD is to facilitate efficient and timely software development efforts through the delegation of oversight and formats for follow-on requirements documents, where traditional JCIDS processes and proscriptive document formats are not supportive of the incorporation of evolving technologies. This flexibility enables faster acquisition outcomes.

Use of the IS-CDD is appropriate:

1. To document capability requirements when an AoA, as a follow-on to a traditional IS-ICD, has identified that an Information System (IS) is a viable materiel approach to be considered.

2. To facilitate the procurement and/or modification of Commercial off the Shelf (COTS) or Government off the Shelf (GOTS) IS products (from DoD, allied, partner-nation, or other U.S. Government agency), including of ​the procurement/modification of COTS/GOTS hardware (when necessary), as a proposed solution to an identified capability gap

*Note: An IS-CDD can advocate and plan for COTS/GOTS hardware refresh over time due to anticipated obsolescence, including modification(s) required for integration, or enhancements necessary to meet the specifications of the IS-CDD.

The IS-CDD is not appropriate:

1. If the software requires a host platform, such as a manned or unmanned vehicle, which does not yet have a validated capability requirement document

2. If the software requirements have already been validated as part of a separate, materiel capability solution​ (e.g. ICD)

3. For hardware development efforts or capturing capability requirements which span a broad scope of combined hardware, software, and/or DOTmLPF-P efforts

4. To propose increases in quantities of previously fielded IS without modification, which are not addressed by an IT Box—such increased quantities should be addressed using a DOTmLPF-P Change Recommendation (DCR)

5. ​To document capability requirements for Defense Business System (DBS) capabilities

All CDDs specify warfighter capability requirements in terms of performance attributes that pertain to a particular system.

- These include Key Performance Parameters (KPPs), Key System Attributes (KSAs), and Additional Performance Attributes (APAs). These KPPs, KSAs, and APAs support the development of one or more increments of a particular materiel capability solution.

- Your “draft” IS-CDD (NOT submitted to the Joint Staff; approved at Service level) is needed to support Milestone A and the Technology Maturation and Risk Reduction (TMRR) phase.

- Your “validated” IS-CDD (“validated” by the Joint Staff or other “validation” authority) is needed for the Development Request for Proposal (RFP) Release review and Milestone B.

- NOTE: A validated IS-CDD is also required for Milestone C; however, if there are no changes from the IS-CDD validated prior to Milestone B, you may proceed directly to Milestone C without revalidation.

- If performance attributes change as a result of the EMD phase, you must submit your updated CDD for review and revalidation IAW the deliberate staffing section of the JCIDS Manual.

- In cases where the Milestone Decision Authority (MDA) waives either Milestone A or B and decides to conduct an Engineering and Manufacturing Development (EMD) acquisition phase, you will need to move your IS-CDD to validation BEFORE the release of the EMD RFP – OR the beginning of the EMD phase of acquisition, whichever comes first.

- In cases where the MDA combines Milestone B and C (like high-cost first articles of spacecraft and ships…), your IS-CDD is the authoritative document for the first article produced during EMD without the need for updated CDDs.

- You should develop your IS-CDD using an integrated product team (IPT) comprised of the major stakeholders.

- The Requirements Manager from the sponsoring organization leads the IPT that includes representatives from:

- Service Requirements Sponsor (Army Futures Command, Air Force Major Command, Navy (OPNAV), USMC (MCCDC), and US Space Force (USSF))

- Program Management Office and supporting Acquisition Commands

- Operational and Developmental Test Organizations

- Intelligence Agency (Service and DIA)

- Best Practice: assemble your IS-CDD IPT early in the Materiel Systems Analysis (MSA) phase, during the conduct of the Analysis of Alternatives (AoA).

- Assemble the following documents for your IS-CDD reference library (for a “draft” IS-CDD that supports the Technology Maturation & Risk Reduction phase):

- The Capabilities Based Assessment (CBA) Report and other studies that supported development of the ICD.

- The validated ICD.

- Materiel Development Decision ADM.

- Analysis of Alternatives (AoA) Report.

- Post-AoA review results and recommendations to the MDA.

- Results of the Goal Establishment Meeting (GEM) addressing the AoA results, and the completed Program Cost, Fielding, and Performance Goals (see DoDI 5000.85, Appendix 3C, section c. and figures 3 and 4).

- For a Validated IS-CDD to support the Development RFP Release Decision, you need:

- Current CONOPs

- JCIDS Manual (CAC required)

- Service CDD Guidance (RM Community of Practice)

- Test reports from the TMRR Phase, such as Early Operational Assessments (EOAs)

- Program and technical review results

- Cost, performance, and schedule trades agreed to by your team and the PM

- AoA updates (if applicable)

- Operational Mode Summary/Mission Profile

- Information required to support a DRFPDR decision (see AAFDID). In addition to any updates to documents in the previous chart, you need to ensure close coordination with the PMO on the additional documents listed in the table on the next chart.

- References Required/Suggested by JCIDS Manual

- DoDAF Views generated during prior analysis

- Latest approved threat products/analysis from the Defense Intelligence Enterprise (DIE).

- DIA Instruction 5000.002, Intel Threat Support for MDAPs (posted to RMCoP)

- Universal Joint Tasks (UJTs) or Equivalent Service Tasks

- DoD Guidebook for Electromagnetic Spectrum Survivability (posted to KM/DS)

- Cyber Survivability Endorsement Implementation Guide (posted to KM/DS)

- Spectrum supportability compliance (DoDI 8320.05 and DoDI 4650.01)

- Joint Training Technical Interoperability Standards and Technical Approaches (see JCIDS Manual, Appendix C, Enclosure B, part 2.5.7.5, page B-C-13)

- DoDI 8510.01, Risk Management Framework for IT Systems

- Joint Capability Area (JCA) Taxonomy and Definitions (CAC required)

Organize Your Work

- Proposed Content of a Draft IS-CDD to Support TMRR:

- A draft IS-CDD outlines the minimum essential information for technology maturation and preliminary design. This draft IS-CDD is approved at Service level and not provided to the Joint Staff. Don’t confuse this draft IS-CDD with a “draft” version of the full IS-CDD required later in the JCIDS process.

- Your draft IS-CDD’s content must be sufficient to inform the RFP for the TMRR contract. You’ll need to determine your Service policy for this document (Examples: Army Abbreviated CDD and Air Force AF/A5R Requirements Development Guidebook, Vol 3, Guidelines for JCIDS Document Development – both posted to RMCoP)

- Operational Context (IS-CDD Section 1). Summary of Service and joint concepts and/or CONOPS.

- Capability Discussion (IS-CDD Section 3). Summary of previously validated capability requirements from the ICD.

- Program Summary (IS-CDD Section 4). Focus on synchronization of System of Systems (SoS) efforts across other CDDs, CPDs, and DCRs, and identification of dependencies on any legacy or future enabling capabilities.

- Development KPPs, KSAs, and APAs (IS-CDD Section 5). Initial/draft performance attribute(s) from the AoA or similar studies. Also provide initial/drafts of the mandatory attributes, or justification for why they are not applicable.

- Other System Attributes (IS-CDD Section 6). Attributes other than KPPs/KSAs/APAs which require significant efforts during the TMRR phase of acquisition.

- Interoperability (IS-CDD section 7). How the system will interoperate within the joint environment including any physical or net-ready interoperability effects on joint service operations or operations with allies and partners.

- Technology Readiness (IS-CDD Section 10). List “critical technologies” the PM has identified that need to be matured during the TMRR phase.

- DoDAF views and associated data supporting the capability requirements document must be made accessible through a URL to your architecture data repository.

- Refer to the Warfighter Mission Area – Architecture Federation and Integration Portal (WMA-AFIP), and on SIPRNET - https://wmaafip.csd.disa.smil.mil.

- Figure B-28, JCIDS Manual, lists the DoDAF Views that support all capability requirements documents. Figure B-31 identifies additional net-ready artifacts/views.

- Only the DoDAF views specified by the document formats, or additional views deemed appropriate by the Sponsor, should be included in the ICD/IS-ICD/SW-ICD.

- The Operational View 1 (OV-1) must be included in Section 1, Operational Context, of the CDD and IS-ICD. In the appropriate text of refer to the DoDAF views required by table B-28 you posted to your data repository as necessary, and to ensure consistency.

- DoDAF Data for Net-Ready Certification.

- In addition to required architecture data and associated artifacts/ views identified in JCIDS Manual Figure B-28 for all capability requirements documents, Figure B-31 identifies additional net-ready artifacts/ views for a CDD and IS-CDD.

- These views are required for Net-Ready certification.

- See the DoDAF Primer, Appendix H, JCIDS Manual, for a description of all the DoDAF products that apply to JCIDS documents.

- Figures B-28 and B-31 in the JCIDS Manual identify who is responsible for development of the DoDAF architecture data, the IS-CDD sponsor, the program office, or jointly developed by the sponsor and program office.

General guidance on using the RDW includes:

- The sections and sub-sections in the RDW are laid out sequentially according to the elements that the JCIDS Manual requires within your document.

- Most are MANDATORY and will show an error in RED FONT if you do not address them.

- If you don't believe a mandatory element is applicable to your document, simply enter, "XXX is not applicable because....," or similar verbiage.

- If you choose to address a mandatory required element within another sub-section (perhaps in conjunction with another element), you may skip over (leave blank) these mandatory sections, just bypass the error message. Just make sure you address each requirement somewhere in the relevant section.

- Some sub-sections are marked "Optional." These can be skipped (left blank) without showing an error. HOWEVER, if the element is applicable to your document, ensure to address it SOMEWHERE in your document.

- You are able to use rich text (e.g. bold, italicize, underline, red or black font, etc.) within many of the writing sections (not all). Some are constrained due to the requirements in the JCIDS Manual.

- If you choose to cut and paste text from another source, make sure you convert it to the font you are using throughout the document. According to the JCIDS Manual, for the body of the document you have two choices: 1. Times New Roman, Regular, and size 12, or; 2. Bookman Old Style, Regular, and size 12. These are the only fonts (and sizes) allowed by the JCIDS Manual for the body of the document.

- The default font used in the document body sections of the RDW is Times New Roman, Regular, size 12.

- For content within tables, please ensure the font is consistent and either Arial or Calibri, size 10, per the JCIDS Manual.

- The default font used in the tables within the RDW is Arial, size 10.

- Please refer to the "RDW post-export to MS Word Actions" section of the Desk Reference, available through the website (https://content1.dau.edu/rdw) for additional formatting required to be performed once you've exported your RDW Document to MS Word.