Joint Combat Capability Developer (JCCD)
Abstract
Primary OUTCOME (objective) for this effort is to identify and develop the capability needs and essential Doctrine, Organization, Training, Materiel, Leadership, Personnel, Facilities – Policy (DOTMLPF) and Policy attributes in support of objective Joint command and control (C2) requirements/capability needs for use in the development of Joint net-enabled and agile C2 capabilities. Strategic Planning Guidance (SPG) directed establishment of a transformation path to achieve a joint command and control capability for DoD - "Strengthening joint operations through ... improved joint command and control is an indispensable step forward in transformation." Unified Command Plan (UCP) 08 assigned USJFCOM as the Joint Force Integrator to lead the development of joint command and control doctrine, concepts, requirements and integrated architectures. Furthermore, DoD Directive 5100.30 (U), 1/5/2006, "Department of Defense (DoD) Command and Control (C2)" established USJFCOM as the advocate for joint command and control in the Department of Defense. Joint Requirements Oversight Council Memorandum (JROCM) 167-03, 22 August 2003 designated USJFCOM as operational sponsor for Net-Enabled Command Capability (NECC) and further delegated NECC (originally named Joint Command and Control (JC2) Capability) non-Key Performance Parameter (KPP) requirement adjustment approval authority to USJFCOM. DepSecDef Memorandum (10 Dec 2008) designates USJFCOM, delegated to the JCCD, as the joint functional sponsor for the Global Theater Security Cooperation Management Information System (G-TSCMIS) for the development of joint requirements. DepSecDef Memorandum (14 Sep 2006) directed capability portfolio management test-cases and empowered CDR USJFCOM as the C2 Capability Portfolio Manager (C2 CPM). USJFCOM J8 has been designated the Joint Capability Developer (JCD) and execution arm of C2 CPM and the C2 Capability Integration Board (C2CIB). The JCD takes direction from the CPM and the C2CIB and authority as appropriate and develops courses of action to source, acquire, and develop Joint net-enabled and agile C2 capabilities in conjunction with the Combatant Commands and Services. JROCM 173-07 (16 July 2007) approved the Net-Enabled Command Capability Increment I Capability Development Document (CDD) and Extensions, and validated the Key Performance Parameters (KPPs). The JROCM further states that the JROC will maintain approval authority for all KPP changes, delegates approval authority oversight for changes to key system attributes (KSA) to the Joint Capabilities Board (JCB), and delegates approval authority for all non-KPP changes to USJFCOM (via the JCCD organization). CJCSI 3265.01 Command and Control Governance and Management (22 Sep 2008) designates USJFCOM as responsible for the functional management of joint C2 requirements and capability development needs (to include GCCS FoS and NECC), formerly managed by JS/J3. USJFCOM executes operational sponsorship of the GCCS-Joint (GCCS-J) and capability development responsibilities of NECC through the JCCD. Finally, Program Decision Memorandum (PDM) II (19 Nov 2007) states that the JCCD and material provider (DISA) in consultation with the users (Combatant Commands and Services) can prioritize the delivery of functionality within already provided funding for the NECC Increment 1 and furthermore that the DOTMLPF-P capability requirements will be defined by the JCCD in consultation with ASD (NII), DISA, Combatant Commands and Services and identified within existing Service, Joint and Agency funding and infrastructure.
Document Details
- Document Type
- Accomplishment
- Publication Date
- Oct 01, 2011
- Source ID
- 5272f2a7c4df536a4aaa97679ebf49a2