FORCEnet Implementation Strategy (2005) / Chapter Skim
Currently Skimming:
3 Joint Capability Development and Department of Defense Network-Centric Plans and Intentions
3 Joint Capability Development and Department of Defense Network-Centric Plans and Intentions
Pages 47-78
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 47... ...
It will focus on creating information networks with new levels of connectivity and integration, which will integrate the force into a joint information network.1 The leadership of the Navy and Marine Corps is committed to providing "flexible, persistent, and decisive warfighting capabilities as part of a joint force."2 At the same time, leadership in OSD is pressing the military departments and the Services to become more responsive to OSD's and combatant commanders' priorities for developing warfighting capabilities and implementing network-centric operations and processes.3 This urging has resulted in the OSD and the Joint Staff's changing, during 2003, all higher-level guidance relevant to FORCEnet implementation. The combination of the naval leadership's commitment to joint warfighting, which includes coalition operations with allies and security partners, and the broader DOD leadership's commitment to strengthening jointness and 1ADM Vern Clark, USN, Chief of Naval Operations; and Gen Michael W
|
From page 48... ...
"Pete" Aldridge, Jr., to provide streamlined processes, alternative functions, and organizations to better integrate defense capabilities in support of joint warfighting objectives.4 The study found that: · Services dominate the current requirements process, focusing on Service programs and platforms rather than on the capabilities required to accomplish combatant command missions; this situation results in an inaccurate picture of joint needs and an inconsistent view of priorities and acceptable risks across the DOD. · Service planning does not consider the full range of solutions available to meet joint warfighting needs; alternative ways to provide equivalent capabilities receive inadequate attention, particularly if the alternative solutions reside in a different Service or defense agency.
|
From page 49... ...
However, the intent of the SECDEF to produce fiscally feasible Joint Programming Guidance directing the Services to acquire specific capabilities is clear. 3.2.2 Joint Capabilities Integration and Development System The new Joint Capabilities Integration and Development System (JCIDS)
|
From page 50... ...
analysis; combatant (JCIDS 3170.01C. 's solutions COCOM, CJCSI System plans; functional FSA, SOURCE: concept Development and analysis; facilities.
|
From page 51... ...
and the GIG. 3.2.3 Joint Battle Management Command and Control The Deputy Secretary of Defense's Management Initiative Decision 912 in early 2003 directed JFCOM to lead efforts to strengthen the organizing, training, and equipping of joint battle management command and control capabilities for combatant commanders.9 JBMC2 is deemed to consist of the processes, architectures, systems, standards, and command-and-control operational concepts employed by the Joint Force Commander.
|
From page 52... ...
The goal of the roadmap is as follows: [to] develop a coherent and executable plan that will lead to integrated JBMC2 capabilities and interoperable JBMC2 systems that in turn will provide net worked joint forces: · Real-time shared situational awareness at the tactical level and common shared situational awareness at the operational level; · Fused, precise, and actionable intelligence; · Decision superiority enabling more agile, more lethal, and survivable joint operations; · Responsive and precise targeting information for integrated real-time of fensive and defensive fires; and · The ability to conduct coherent distributed and dispersed operations, in cluding forced entry into anti-access or area-denial environments.
|
From page 53... ...
They also tell me that "it's not the plan, it's the planning." They understand that the ability to plan and adapt to changing circumstances and fleeting opportunities is the key to rapid victory in the modern battlespace.12 The Chairman of the Joint Chiefs of Staff (CJCS) has directed the commander of JFCOM to carry out the following: · Aggregate key joint operational and interoperability lessons reported by combatant commands, defense agencies, and the Services during OIF and the war on terrorism; · Analyze, categorize, and prioritize these lessons, working with functional capabilities boards; and · Convey recommendations of materiel and nonmateriel approaches for remedies to shortfalls indicated by the lessons learned to the JROC as the basis for recommendations to the SECDEF.13 This effort is leading to the establishment of a permanent JFCOM organization on lessons learned (the Joint Center for Operations Analysis and Lessons Learned)
|
From page 54... ...
In November 2003, the SECDEF issued the "Joint Operations Concept," (JOpsC) as the overarching document that contains the following:18 · A description of how the Joint Force intends to operate within the next 15 to 20 years; · The conceptual framework to guide future joint operations and joint, Service, combatant command, and combat support defense agency concept development and experimentation; and · The foundation for the development and acquisition of new capabilities through changes in doctrine, organization, training, materiel, leadership and education, personnel and facilities (DOTMLPF)
|
From page 55... ...
The Naval Operating Concept for Joint Operations aligns its concepts of Sea Strike, Sea Shield, Sea Basing, and FORCEnet with the Joint Vision 202022 concepts of precision engagement, dominant maneuver, full dimensional protection, focused logistics, and joint command, control, communications, computers, intelligence, surveillance, and reconnaissance (C4ISR) , from which the new functional capabilities categories were derived.
|
From page 56... ...
Atlantic Command (which became JFCOM in FIGURE 3.2 Joint Staff approach for shifting from a bottom-up approach driven principally by the Services to a top-down capabilities-based methodology.
|
From page 57... ...
Red teams were recognized as an essential feature of this activity. The OSD established a Defense Adaptive Red Team as part of the Joint Warfighting Program element retained by the Deputy Under Secretary of Defense for Advanced Systems and Concepts when Joint Experimentation Program funds were transferred to JFCOM.
|
From page 58... ...
, the combatant commands, the Services and Defense Agencies.26 24Rick Kass, Chief Analysis Division, U.S. Joint Forces Command, "Understanding Joint Warfighting Experimentation Methods," presentation to the Committee on the Role of Experimentation in Building Future Naval Forces, May 1, 2002.
|
From page 59... ...
This guidance kept the SJFHQ as the highest priority, but it also directed coordination with combatant commands, Services, Joint Staff, and defense agencies, as well as the inclusion of the following: · Lessons learned from the war on terrorism; · Joint operations in an uncertain environment and complex terrain; · Fast-deploying joint command-and-control structures; · Concepts to provide warfighters at all levels with improved battlespace awareness, correlation and dissemination of mission-specific information, and more closely integrated intelligence, surveillance, and reconnaissance efforts and products; · Joint capabilities enabling the near-simultaneous, integrated, and synergistic employment and deployment of air, land, sea, cyberspace, and space warfighting capabilities, capitalizing on Service concepts and capabilities that enable forward joint forces and those based in the continental United States to deploy, employ, sustain, and redeploy in austere regions and antiaccess and area-denial environments. · Transformational concepts of the Nuclear Posture Review (involving global strike with conventional and special forces in addition to nuclear strike, as well as global information operations)
|
From page 60... ...
Polling the combatant commanders produced 308 items, which were aggregated into those illustrated in Box 3.1.27 The highlighted items indicate priorities that were to be addressed in FY 2004 and FY 2005. 27CAPT Paul Smith, USN, Joint Concept Development and Experimentation Office, U.S.
|
From page 61... ...
The joint battle management command and control roadmap calls for expansion of the Joint Distributed Engineering Plant (JDEP)
|
From page 62... ...
Year Fiscal for proposed as plan gaming Va. war Norfolk, Development Command, Concept Forces Joint Joint The U.S.
|
From page 63... ...
30Judith Dahmann, scientific advisor to director of interoperability, Office of the Secretary of Defense for Acquisition, Technology, and Logistics and principal senior staff, MITRE Corporation; and Richard Clarke, JDEP Technical Director, Joint Interoperability Test Command, "Joint Distributed Engineering Plant Technical Framework: Applying Industry Standards to System-of-System Federations for Interoperability," undated. This paper describes the framework, the migration strategy, and progress to date in assessing and applying the technical framework.
|
From page 64... ...
will prepare forces by providing command staffs and units with an integrated live, virtual, and constructive training environment that includes appropriate joint context and that allows global training and mission rehearsal in support of specific operational needs. The thrusts for the JNTC are these: · Improved horizontal training -- building on existing Service interoperability training, · Improved vertical training -- linking component and joint command and staff planning and execution, · Integration training -- enhancing existing joint exercises to address interoperability training in a joint context, and · Functional training -- providing a dedicated joint training environment for functional warfighting and complex joint tasks.
|
From page 65... ...
The schedule for these Web-based networks includes the following milestones for training transformation: · Joint knowledge development and distribution capability milestones include: -- An initial Web-based curriculum for joint military leader development by January 2004, -- An initial Web-based delivery capability for joint individual education and training resources by February 2005, and -- The transitioning of initial joint education and training prototype efforts to implementing organizations by March 2006, and to international coalition partners, international organizations, and nongovernmental organizations by October 2009. · JNTC milestones include: -- Provision of a joint context with command, control, communications, computers, intelligence, surveillance, and reconnaissance to major Service training events and joint command and staff training events by October 2005; -- Use of the joint training system to link lessons learned from military operations, joint training, experimentation, and testing to the development and assessment of joint operational capabilities by October 2005; -- Demonstration of a deployable JNTC and mission-rehearsal capabilities by October 2007; and -- Creation of an initial Web-based delivery capability for operational mission planning and rehearsal by October 2005.
|
From page 66... ...
13. 34 These include DOD Directive 8100.1, "Global Information Grid Overarching Policy," September 19, 2002; Deputy Secretary of Defense Memorandum, "Global Information Grid Enterprise Services: Core Enterprise Services Implementation," November 10, 2003; and Assistant Secretary of Defense for Networks and Information Integration Guidance Memorandum, "Global Information Grid Enterprise Services," February 2004.
|
From page 67... ...
Communications Architecture (TCA) 3.6.2 Components of the Global Information Grid Table 3.3 describes the eight investment areas leading to the realization of the GIG.
|
From page 68... ...
service NOTE: GIG Arch v2, Global Information Grid (GIG) Architecture, Version 2.0.
|
From page 69... ...
Data are stored in NCOW RM, DOD Net-Centric Data Strategy public space and advertised (tagged)
|
From page 70... ...
Ground/Surface collections. Systems Joint Command Command and control FY 2010 Schedule.
|
From page 71... ...
U.S. naval forces also participate in demonstrations, exercises, and operations scheduled and run by allies and coalition partners.
|
From page 72... ...
Through routine interaction with allies and coalition partners, U.S. naval forces are well positioned to further FORCEnet implementation in this context.
|
From page 73... ...
This success derived from "a willingness to innovate, close and open ties to the technical community, unblinking candor in performance analysis, dedicated organic submarines focused on development, top-notch personnel, military and civilian, and a strong, clear mission focus."37 The defense planning, joint capabilities integration and development, joint concept development and experimentation, JBMC2, joint testing, joint training, GIG development and acquisition processes, and coalition considerations described in this chapter are all separate activities with little interaction. Proposals to organize these activities around mission areas have proven difficult to implement for the large bureaucracies involved in each activity.
|
From page 74... ...
-- The new Joint Programming Guidance from the OSD will direct a greater portion of DON resources toward OSD and combatant commander priorities. If the new process works as intended and FORCEnet is perceived as providing joint capabilities responsive to combatant commander needs, FORCEnet is less likely to have to compete for funding within the available discretionary funds of the Navy and Marine Corps that will have been reduced as a result of mandated spending on joint capabilities.
|
From page 75... ...
In participating in JFCOM experimentation activities, the Navy and Marine Corps need to keep their activities focused so that they do not become overwhelmed by the much greater JFCOM experimentation resources. -- While JFCOM is the executive agent for joint experimentation, the regional combatant commands are becoming an increasing focus for joint concept development and experimentation.
|
From page 76... ...
: Build on current interactions with regional combatant commands in order to grow the relationship between naval and joint concept development and experimentation. This means ensuring both that naval concepts are properly embodied in joint concepts and that they reflect the needs of the joint concepts.
|
From page 77... ...
· Recommendation for the fleet commands and MEFs: Work with the combatant commands to which they are assigned in order to understand and feed into the naval requirements process the capabilities needed by the combatant commands from naval forces. The CFFC, and Commanding General, MCCDC, would act as the intermediaries for feeding this information from the fleets and MEFs into the program planning processes of the Navy and Marine Corps.
|
From page 78... ...
: Coordinate with the Under Secretary of Defense for Personnel and Readiness to exploit DOD investments in Training Transformation to support FORCEnet development. The committee recommends that CFFC and Sea Trial operational agents schedule fleet battle experiments in exercises employing the joint national training capability.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.