FORCEnet Implementation Strategy (2005) / Chapter Skim
Currently Skimming:
7 Implementation Strategy
7 Implementation Strategy
Pages 186-209
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 186... ...
The previous chapters of this report deal with the various aspects of FORCEnet implementation strategy. From that work, the following set of objectives for the strategy can be abstracted: · Provide clarity of purpose.
|
From page 187... ...
7.2 CLARITY OF PURPOSE The definition of FORCEnet is as follows: [FORCEnet is] the operational construct and architectural framework for naval warfare in the information age that integrates warriors, sensors, networks, com mand and control, platforms, and weapons into a networked, distributed, com bat force that is scalable across all levels of conflict from seabed to space and sea to land.1 This definition is adequate as a point of departure for the implementation of FORCEnet capabilities, but further elaboration is necessary in order to provide clarity of purpose to all those involved in the implementation.
|
From page 188... ...
As one final point, the discussion here indicates that FORCEnet -- as concepts of employment and architectures -- is composed of those processes and descriptive items that guide the implementation and realization of network-centric capabilities in the force rather than being the implemented components themselves. The implemented components are referred to using "FORCEnet" as a modifying term -- for example, "the FORCEnet Information Infrastructure." To provide better clarity of purpose, the committee recommends the following: · Recommendation for OPNAV, NETWARCOM, and MCCDC: Articulate better the meaning of the terms "operational construct" and "architectural framework" in the description of FORCEnet and indicate how FORCEnet implementation measures relate to each of these concepts.
|
From page 189... ...
3The study also presents implementation responsibilities for the Marine Corps (Table 4.2) , but the extent of the study's examination did not allow it to develop an assessment of those responsibilities as it did for the Navy.
|
From page 190... ...
190 FORCENET IMPLEMENTATION STRATEGY CFFC Operational Concept and Requirements Development OPNAV ASN(RDA) Program Acquisition and Formulation and Engineering Resource Execution Allocation FIGURE 7.1 Implementing FORCEnet.
|
From page 191... ...
IMPLEMENTATION STRATEGY 191 mand ship, and NETWARCOM is conducting the Trident Warrior series of exercises. NETWARCOM's experimentation thus focuses largely on the FnII.
|
From page 192... ...
Each of these NCPs is further divided into Mission Capability Packages. Those for the FORCEnet NCP are Intelligence, Surveillance, and Reconnaissance; Common Operational and Tactical Pictures; and Networks.
|
From page 193... ...
led the first meeting of the FORCEnet EXCOMM to address FORCEnet implementation issues. The subjects treated included establishing a FORCEnet implementation baseline and redirecting some current-year funds to support FORCEnet objectives.
|
From page 194... ...
194 FORCENET IMPLEMENTATION STRATEGY the rapid development of capability in many of the briefings that it received. Often, no near-term capability delivery (e.g., within 1 year)
|
From page 195... ...
IMPLEMENTATION STRATEGY 195 · Operational concept and requirements development -- program formulation and resource allocation. In this interaction, the requirements developed under the direction of the CFFC need to be reflected adequately in the program development and prioritization activities of the N6/N7.
|
From page 196... ...
196 FORCENET IMPLEMENTATION STRATEGY formulation and acquisition functions, to ensure that adjustments in program execution are consistent with program intent and best serve the overall need of providing forcewide FORCEnet capability. Options to consider include establishing (1)
|
From page 197... ...
The purpose of this plan would be to ensure senior visibility in this area and senior scrutiny of FORCEnet activities and consequent motivation for conducting these activities.8 (Recommendation 18) 7.4 FORCEWIDE PERSPECTIVE FOR MATERIEL DEVELOPMENT As repeatedly stated, FORCEnet applies to the whole naval force -- weapons, sensors, command-and-control systems, communications, and so forth.
|
From page 198... ...
Volume II is a list of almost 300 mandated standards applying principally to the information infrastructure that compliant systems must satisfy. While Volume I generally recognizes the extent of FORCEnet's applicability, neither volume adequately defines the architectural boundaries or invariants, nor provides mechanisms for allocating functionality among the components.
|
From page 199... ...
For a general discussion of the open architecture initiative, see CAPT Richard T Rushton, USN, Office of the Chief of Naval Operations (N76)
|
From page 200... ...
The committee thus recommends the following: · Recommendation for OPNAV: Adopt the Net-Centric Checklist of the ASD(NII) in place of the OPNAV FORCEnet Compliance Checklist, adapting it if necessary to accommodate specific aspects of naval warfare.
|
From page 201... ...
Network control, distributed information management, and information assurance are three matters warranting particular attention in this regard for FORCEnet implementation. Even in the case of a well-architected system with a proper systems engineering process, unanticipated integration difficulties can still occur when the overall system is assembled from its components.
|
From page 202... ...
Thus, a successful FORCEnet implementation strategy can be the model for realizing network-centric capabilities across the DOD. 15For example, see ADM Vern Clark, USN, Chief of Naval Operations; and Gen Michael W
|
From page 203... ...
The fleet commands are a natural vehicle for interacting with the combatant commands in this regard, as has been the case, such as in the interaction of the Pacific Fleet and its components with the PACOM. · The derivation of capabilities required by joint forces (and likewise their naval components)
|
From page 204... ...
204 FORCENET IMPLEMENTATION STRATEGY · Recommendation for NETWARCOM, NWDC, and MCCDC: Continue to work with JFCOM to broaden its experimental perspective, with particular emphasis on joint operations at the tactical level. If necessary for these organizations to maintain focused commitment in the face of far larger JFCOM resources, the CFFC, and the Commanding General, MCCDC, should provide guidance on the issues to be addressed and the partitioning of naval involvement in JFCOM, regional combatant command, and Service concept development and experimentation activities.
|
From page 205... ...
· 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 the 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 206... ...
7.5.3 Acquisition and Engineering Execution The Naval Services should participate actively with joint GIG programs during their execution for two reasons. First, the Naval Services have specific expertise that they can bring to the programs to aid their execution.
|
From page 207... ...
Furthermore, since NCES as currently envisaged assumes continuous communications connectivity, its use requires some mixture of antenna technology and alternative relay paths to overcome antenna blockages that interrupt connectivity. Fully exploiting enterprise services in a naval context will require considerable exploration and potential technology development.
|
From page 208... ...
. These policies and compliance criteria will constrain naval programs, but at the same time they will provide significant external leverage for achieving FORCEnet objectives -- that is, realizing network-centric capabilities within the naval forces.
|
From page 209... ...
IMPLEMENTATION STRATEGY 209 sary at the tactical level of warfare, since architectural development of the GIG has not explored that level to a significant extent.
|
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.