Downloaded from https://www.everyspec.com refresh the TOC and ensure all page and paragraphs correlate properly. Add a list of figures, if 269 used, to complete the TOC. If you manually create a TOC or have added a list of tables and 270 figures, check this for accuracy as your last editorial review of the CDD. 271 272 (3) Revision History . Use the revision history table below for configuration management 273 of the Draft CDD. Ensure the information is consistent with the revision history table and the 274 cover entries for the Draft Version and Date . 275 276 277 (4) Points of Contact (POCs).
POCs should cover the primary writer/editor at the 278 proponent and a Program Manager Representative if available/appropriate. Ensure at least two 279 Proponent level POCs are listed, to include valid SIPRNET (.smil) e-mail addresses. All 280 staffing post-ARCIC Validation (ARSTAF & JSTAF) takes place on SIPRNET and staffing 281 comments will be returned to the proponent/document sponsor on SIPRNET. It is imperative 282 that the proponent/document sponsor be prepared to operate in a SIPRNET environment. 283 284 285 Note: Standard paragraph numbering was restarted at this point to allow for consistency 286 between the guide and the CDD Template in paragraph 1. 287 288 1.
Capability Discussion . Limit this paragraph to one page. Cover the four areas outlined as 289 subparagraphs in the attached template. 290 291 a. Discuss the operating environment of the system. Address how the capability will be 292 employed on the battlefield and where it will be employed and/or based. 293 294 b. If the CDD is part of a FoS or SoS solution, discuss the source ICD and the related CDDs, 295 CDDs, integrating DOTMLPF and policy changes and required synchronization. 296 297 c. It is critical to “list” direct predecessor documents that support the CDD.
If the capability 298 development effort preceded the implementation of JCIDS, list the requirements document that 299 supports and underpins the CDD, i.e. the Operational Requirements Document (ORD). 300 301 d . Identify the JCAs (Tier 1 and 2) in which the capabilities being delivered through the CDD 302 directly contribute. “List” only the applicable JCAs, there is no requirement to provide rationale 303 for their inclusion. However, there should be a high correlation to the capability advocated for 304 8 Draft Version Date Purpose 0.1 Day-Mon-Yr Initial Draft Developmental (Worldwide) Staffing ARCIC Staffing/Validation Phone Number Name Agency/Organization Email Address & DSN NIPR: SIPR:
NIPR: SIPR: