Текст документа
16 June 2009
Downloaded from https://www.everyspec.com TRADOC Capability Development Document (CDD) Writer’s Guide Version 1.5 16 June 2009 The proponent for this guide is the ARCIC Operations, Plans and Policy Division, Army Capabilities Integration Center (ATFC-O), TRADOC. This guide is one of a series of web-based publications available at https://www.us.army.mil/suite/kc/5232873 and the ARCIC Portal at https://cac.arcicportal.army.mil/ext/jcids/default.aspx . Users are encouraged to send comments using MS Word Track Changes approved by a COL or equivalent to Monr.arcicgatekeeper@us.army.mil. Updates will be uploaded as changes become necessary.
Стр. 1
Revised paragraph 14, Other DOTMLPF and Policy Considerations, in response to an Army Audit Agency preliminary recommendation in an ongoing JCIDS audit that “CDDs/CPDs don’t contain all the necessary DOTMLPF requirements to support acquisition for a M...
Downloaded from https://www.everyspec.com Summary of Changes 1 2 Version 1.4 3 Added subparagraph 14.i (6) Corrosion Prevention and Control (CPC). 4 5 Added subparagraph 14.i (7) Item Unique Identification (IUID). 6 7 Version 1.5 8 Revised paragraph 14, Other DOTMLPF and Policy Considerations, in 9 response to an Army Audit Agency preliminary recommendation in an ongoing 10 JCIDS audit that “CDDs/CPDs don’t contain all the necessary DOTMLPF 11 requirements to support acquisition for a Milestone C decision. The 12 information contained in the documents is inconsistent, generalized and 13 incomplete.” 14 15 1
Стр. 2
NOTE: This version of the CDD Writer’s Guide is based upon the instructions outlined in the CJCSI 3170.01G, Joint Capabilities Integration and Development System,1 Mar 09, the online Manual for the Operation of the Joint Capabilities Integration and ...
Downloaded from https://www.everyspec.com CDD Instructions and Template 16 17 NOTE: This version of the CDD Writer’s Guide is based upon the instructions outlined in the 18 CJCSI 3170.01G, Joint Capabilities Integration and Development System,1 Mar 09, the online 19 Manual for the Operation of the Joint Capabilities Integration and Development System, 1 Mar 20 09 , and applicable Army and TRADOC regulations. This is supplemental information and not 21 intended to replace or replicate the JCIDS Manual in its entirety. 22 23 1. CDD Format and template . The CDD format described below and included on the attached 24 template is mandatory for all Army-developed CDDs.
The information in this guide complies 25 with instructions provided by the Office of the Secretary of Defense (OSD), Chairman of the 26 Joint Chiefs of Staff (CJCS), and Headquarters, Department of the Army (HQDA) and leads the 27 user through each paragraph of the CDD format. Annotations for each paragraph and entry 28 describe the information that it must contain, the source of that information, and how that 29 information is developed in analyses. Use the template below to develop the CDD. 30 31 Jun 09) .doc 32 CDD Template (16 33 a. Each subparagraph should be numbered to facilitate requirements correlation and 34 traceability, and for ease of identifying issues during staffing.
Use conventional alpha-numeric 35 numbering of paragraphs. The use of scientific numbering is unacceptable . 36 37 b. CDDs must be submitted in MS-Word (6.0 or greater) format. Use Times New Roman, 12 38 pitch font. Do not submit document in Microsoft 2007 format, use 97-2003 compatible 39 documents with the extension “.doc” HQDA is not postured to accept them and the G3 40 automated staffing tool, Capabilities and AROC Management System (CAMS), does not 41 recognize them as valid files. 42 c.
Architecture products should be embedded into the MS-Word file for ease of review during 44 the staffing process except the SV-6 which is provided as a separate MS Excel file or an 45 embedded Excel file in Appendix A – Net-Ready KPP Products. 46 43 47 d. All CDDs must be clearly labeled with draft version number, date, classification, and 48 include any caveats regarding releasability, even if UNCLASSIFIED. Paragraphs that contain 49 non-releasable information (allies or industry) will be marked appropriately. 50 51 e. Draft documents must be submitted with continuous line numbers displayed. 52 53 f.
The Manual for the Operation of the Joint Capabilities Integration and Development 54 System contains the format to be used for the body of the CDD. The CDD should be no more 55 than 35 pages in length. ARCIC’s internal “goal” is to keep the body of the CDD to 10 pages or 56 less. 57 58 2
Стр. 3
NOTE: This version of the CDD Writer’s Guide is based upon the instructions outlined in the CJCSI 3170.01G, Joint Capabilities Integration and Development System,1 Mar 09, the online Manual for the Operation of the Joint Capabilities Integration and ...
Downloaded from https://www.everyspec.com g. The Executive Summary must be no more than two (2) pages. 59 60 h. Do not use photos, symbols, or logos on the front page as part of the title page, or in other 61 locations throughout the document. 62 63 i. There are 3 mandatory Appendices listed for all CDDs. Ensure the appendix names 64 conform exactly to what is prescribed. Innovation is this area is not appropriate. The only 65 exception is supporting analysis, it should be added as appendix D. 66 67 (1) Appendix A. Net-Ready KPP Products. 68 69 (2) Appendix B. References. 70 71 (3) Appendix C. Acronym List. 72 73 (4) Appendix D. Analysis. 74 75 j.
Supporting Documents are not mandatory, but provide supporting information relevant to 76 the CDD. Supporting documents should be submitted with the draft CDD forwarded to ARCIC 77 for validation. Submit them as a separate file labeled as “Supporting Documents for XXX 78 CDD.” Examples of supporting documents are: 79 80 (1) Operational Mode Summary/Mission Profile (OMS/MP). The OMS/MP, if required, 81 should be developed to support the CDD submission. 82 (2) Basis of Issue Guidance (BOIG). The BOIG is a clear articulation of the units and 84 amount of equipment projected to be fielded to the unit.
If the information can be displayed in 85 less than 1 page, it will be captured in paragraph 12, Assets required to Achieve Initial 86 Operational Capability (IOC,) then a separate supporting document for BOIG is not necessary. 87 83 88 (3) System Training Plan (STRAP). If needed, an initial STRAP should be developed on a 89 parallel path with the CDD. Submit early in the CDD development process to give ATSC 90 sufficient time to review and approve the STRAP or STRAP Waiver if the proponent determines a 91 STRAP is not necessary. 92 93 (4) Template for Supporting Documents. 94 95 Supporting Documents template C 96 97 2. Considerations. 98 99 a. Resource Informed .
Determine if adequate resources are available to develop the 100 capability as envisioned in the CDD prior to writing the document. There is no mythical pot of 101 “new money” waiting for a claimant. If there are not sufficient resources for RDTE or at least a 102 3
Стр. 4