FORCEnet Implementation Strategy (2005) / Chapter Skim
Currently Skimming:
Executive Summary
Executive Summary
Pages 1-10
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 1... ...
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 The CNO has requested that the Naval Studies Board of the National Research Council (NRC) provide advice regarding both the adequacy of this definition and the actions required to implement FORCEnet (see Chapter 8 for the terms of reference)
|
From page 2... ...
· Base resource allocation decisions on packages that reflect networkcentric operational concepts. · Strengthen architectural development and systems engineering capabilities.
|
From page 3... ...
Accept That FORCEnet Has No Fixed End State Recommendation for the CNO and the Commandant of the Marine Corps (CMC) : Promote as a guiding principle that the realization of FORCEnet capabilities will require a process of continuous evolution involving the close coordination and coupling of the individual departmental functional processes -- operational concept and requirements development, program formulation and resource allocation, and acquisition and engineering execution.
|
From page 4... ...
However, this committee struggled with the challenge of finding mechanisms to propose for coordinating the responsibilities of OPNAV for program formulation and resourcing with the responsibilities of the acquisition community and for setting short-term and mid-term goals for the entire FORCEnet enterprise.5 Statutory requirements that program executive officers (PEOs) report directly to their Service acquisition executives (the Service acquisition executive for the Navy is the ASN(RDA)
|
From page 5... ...
In considering these options, the committee noted that neither of them would appropriately link the requirements and acquisition processes to the needs of the operational community. Accordingly, the committee discussed the possibility that, in parallel with either of these options, the CNO might establish measurable FORCEnet capability goals with required dates, as well as an annual FORCEnet master plan, and charter the Commander, Fleet Forces Command (CFFC)
|
From page 6... ...
Base Resource Allocation Decisions on Packages That Reflect Network-Centric Operational Concepts Recommendation for the N6/N7 and N8: Develop resource-allocation methods directed at realizing forcewide FORCEnet capabilities. Instead of basing the methods on the current Naval Capability Packages, the Navy should instead use "packages" that inherently reflect network-centric operational concepts.
|
From page 7... ...
Materiel must be specified, developed, and acquired in accordance with an overarching FORCEnet architecture.11 The committee does not find that the draft FORCEnet Architecture and Standards developed by the Space and Naval Warfare Systems Command (SPAWAR) 12 provides optimal guidance for architecture development: Volume I primarily surveys potential FORCEnet components without venturing into functional allocation, and Volume II primarily directs interoperability standards for the FnII.
|
From page 8... ...
The Naval Services must provide capabilities that fulfill combatant commanders' needs and make sure that the relevance of these capabilities is understood. The committee expresses its concern that the Fleet commands and Marine Expeditionary Forces do not appear to be effectively feeding the needs of combatant commanders into the CFFC and MCCDC requirements processes.
|
From page 9... ...
The challenge for DON will be to be prepared to exploit GIG capabilities as they come online, while pursuing science and technology to meet naval-unique challenges such as the antenna and submarine problems just cited as well as to address the information-management problems specific to naval operations. While the highest priority should be given to ensuring robust connectivity across naval units and to resolving naval information-management challenges, DON will also have to contribute to meeting challenges common to all network-centric operations, such as ensuring the security and reliability of mobile network infrastructure.
|
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.