ENCLOSURE C INFORMATION TECHNOLOGY REQUIREMENTS OVERSIGHT AND MANAGEMENT 1. Background: IT programs are dynamic in nature and have, on average, produced improvements in performance 12-18 months. In recognition of this, the JROC requires that IT programs have the flexibility and the planning in place to incorporate evolving technologies throughout the lifecycle of the program. 2. Purpose. The purpose of the “IT Box” is to describe the overall bounds of an IT program in order to facilitate program initiation, as well as to reduce subsequent return trips to the JROC for approval of improved capabilities as the program is executed. The information in the chart will be provided to the JCB/JROC as part of the approval process for any IT program CDD. For programs beyond Milestone B, the IT Box will be included in the approval process for their CPD. 3. Definition. For the purposes of this section, the “IT Box” applies to systems where there is no need to develop hardware systems (i.e., they use commercial off-the-shelf hardware). Research and development funding is spent solely on software development. 4. Description. The four sides of the “IT Box” (Figure C-1) are intended to present and frame the complete program for JCB and JROC members using one slide. The information covers organization and oversight of the program, hardware refresh and system enhancements, integration, application and system software development, and KPP. These four areas should provide a clear understanding to the JCB and JROC that the program has an oversight
an explanation and an electronic copy of whatever alternative analysis has been performed will be made available or attached. 7. CPD Review and Approval. A CPD is written, validated, and approved to support the Milestone C decision for each increment. Unlike the CDD, the CPD is always specific to a single increment and is normally not updated. 8. CPD Publication and Archiving. Approved CPDs (SECRET and below), regardless of JPD, will be posted to the KM/DS tool so that all JCIDS documents are maintained in a single location. 9. System Capabilities. The CPD identifies, in threshold/objective format, the specific attributes that contribute most significantly to the desired operational capability. The focus of these attributes is fundamentally different from that of the attributes provided in the CDD. The CDD values were used to guide the acquisition community in making tradeoff decisions between the threshold and objective levels of the stated attributes. After critical design review, these tradeoff decisions have been made and a more precise determination of acceptable performance can be stated in the CPD. A range of expected performance, provided by the PM, is specified by the expected production threshold and objective value for each attribute or KPP. a. The production threshold and objective values specified for the attributes in the CPD may be refinements of the development threshold and objective values documented in the CDD. Each production threshold listed in the CPD represents the minimum performance that the PM is expected to deliver for the increment based on the results of critical design review. In operational test, a system is required to demonstrate that it can satisfy all KPP and KSA thresholds listed in the CPD for this increment. b. Each production threshold value may be adjusted, as required, to account for post-critical design review estimates and for manufacturing, technical, and other risks. KPP, KSA, and other performance attribute threshold values in the CPD are generally expected to be equal to or better than the corresponding CDD threshold values. However, there may be cases where CDD KPP, KSA, and/or non-KPP threshold values are reduced in a CPD. When this occurs, the following questions must be answered in the CPD: (1) Will the capability still provide sufficient operational effectiveness as defined in the source ICD? (2) If the new capability will replace a fielded capability, will it still provide equal or better overall operational effectiveness than the fielded capability?
ENCLOSURE J REFERENCES a. CJCSI 3170.01 Series, “Joint Capabilities Integration and Development System” b. DODI 5000.02, 2 December 2008, “Operation of the Defense Acquisition System” c. JROCM 261-06, 20 Dec 06, “Cost, Performance and Interdependency Chart Implementing Directive.” d. JROCM 074-07, 29 Mar 2007, “System Training as a Selective Key Performance Parameter Process Action Plan.” e. JROCM 008-08, 14 Jan 2008, “Leveraging Technology Evolution for Information Technology Systems” f. 130-08, 20 Jun 2008, “Assignment of Joint Potential Designators and Coordination by Combatant Commands on Capabilities Documents.” g. 3010.02 series, “Joint Operations Concepts Development Process (JOPSC-DP)” h. DODI 8260.2, 21 January 2003, “Implementation of Data Collection, Development, and Management for Strategic Analyses” i. Paper on Conducting a Capabilities-Based Assessment (CBA) Under the Joint Capabilities Integration and Development System (JCIDS),” JCS J-8/Force Application Assessment Division, January 2008 j. “Joint Capabilities Integration and Development Systems (JCIDS) Analysis Code of Best Practice (COBP),” TRAC-TD-05-012, June 2005 k. “Analysis Handbook: A for Performing Analysis Studies for Analyses of Alternatives or Functional Solution Analyses,” Office of Aerospace Studies, Air Force Materiel Command, July 2008 l. DODD 2000.19E, 14 February, 2006, “Joint Improvised Explosive Device Defeat Organization” m. CJCSI 3470.01 Series, “Rapid Validation and Resourcing of Joint Urgent Operational Needs (JUONS) in the Year of Execution” n. Ronald Reagan National Defense Authorization Act 2005 (PL 108-375), Section 141
o. DODM 5002.02, xx December 2008, “Department of Defense Reliability, Availability, Maintainability and Cost Rationale Report Manual” p. DODD 4630.5, 5 May 2004, “Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS)” q. DODI 4630.8, 30 June 2004, “Procedures for Interoperability and Supportability of Information Technology (IT) and National Security Systems (NSS)” r. CJCSI 6212.01 series, “Interoperability and Supportability of Information Technology and National Security Systems” s. “DOD Architecture Framework, Version 1.5,” 23 April 2007 t. DODD 4650.1, 8 June 2004, “Policy for the Management and Use of the Electromagnetic Spectrum” u. DODD 8100.1, 19 September 2002, “Global Information Grid (GIG) Overarching Policy” v. Joint Publication 3-0, 13 February 2008, “Joint Operations” w. DODD 1322.18, 3 September 2004, “Military Training” x. DOD 5200.1-PH, April 1997, “DOD Guide to Marking Classified Documents” y. CJCSI 3312.01 Series, “Joint Military Intelligence Requirements Certification” z. DODD 8320.2, 2 December 2004, “Data Sharing in a Net-Centric Department of Defense” aa. CJCSI 3137.01 Series, “Functional Capabilities Board Process” bb. 1001.01 Series, “Joint Manpower and Personnel Program” cc. CJCSI 1301.01 Series, “Policies and Procedures to Assign Individuals to Meet Combatant Command Mission-Related Temporary Duty Requirements” dd. 6721.01 Series, “Global Command and Control Management Structure” ee. CJCSI 5120.02 Series, “Joint Doctrine Development System” ff. CJCSI 3500.01 Series, “Joint Training Policy for the Armed Forces of the ” gg. 3500.02 Series, “Joint Training Master Plan 2002 for the Armed Forces of the ” hh. CJCSI 1800.01 Series, “Officer Professional Military Education Policy” ii. CJCSI 3460.01 Series, “Combat Support Agency Review Team Assessments”
jj. JROCM 102-05, 20 May 2005, “Safe Weapons in Joint Warfighting Environments” kk. 10, United States Code, section 167 ll. DODD 2010.6, 10 November 2004, “Materiel Interoperability with Allies and Coalition Partners” mm. DODD 3222.3, 8 September 2004, “DoD Electromagnetic Environmental Effects (E3) Program” nn. “Technology Readiness Assessment Deskbook”, September 2003 oo. DODI 3150.09, 17 September 2008, “The Chemical, Biological, Radiological, Nuclear (CBRN) Survivability Policy” pp. DODD S-5210.81, 18 August 2005, “ Nuclear Weapons Command and Control, Safety, and Security (U)” qq. 3500.04 Series, “Universal Joint Task List (UJTL)” rr. “Capstone Concept for Joint Operations,” Version 3.0, 15 January 2009 ss. DODD 5000.01, 20 November 2007, “The Defense Acquisition System”