Skip to main content

Network-Centric Naval Forces - Overview A Transition Strategy for Enhancing Operational Capabilities (2000) / Chapter Skim
Currently Skimming:

1.2 Leading the Transformations to Network-Centric Operations
Pages 17-22

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 17...
... Such subsystems will be designed and acquired to meet specific requirements of their tasks in the overall mission. For example, a fleet and amphibious force assembled for an expeditionary operation along the littoral will comprise subsystems designed for power projection but will also include antiair, antimissile, and antisubmarine subsystems to protect the naval force while it is projecting power ashore, as well as logistics subsystems to support the forces at sea and ashore.
Read the entire page →
From page 19...
... Joint Service elements or forces and coalition forces operating with the naval forces must also be included. In any mission assignment, from peacetime engagement to combat in a major theater war, NCO systems encompass, as appropriate, all operations from a single weapon engaging a single target to a regional force including one or more fleets and Marine expeditionary forces that might be operating anywhere in the world.
Read the entire page →
From page 20...
... 1.2.2 Creating Network-Centric Operations Systems Transforming the naval forces from platform-centric to network-centric design and operations will require a disciplined approach to developing verylarge-scale integrated systems. New concepts of operation embodying new technical capabilities will have to be developed and then tested in the field, with the test results used to refine the concepts continually and adapt them to changing conditions of threat, environment, and technological advance.
Read the entire page →
From page 21...
... In the current context "interoperability" does not necessarily mean that the characteristics of all subsystems and components must match at the level of waveforms and data formats. Interoperability means that the subsystems must be able to transfer raw or processed data among themselves by any means that can be made available, from actually having the common waveforms and data formats to using standard interfaces or intermediate black boxes enabling translation from one to another.
Read the entire page →
From page 22...
... Actual experimentation by the fleet and Marine force elements is required, to learn how legacy subsystems and their components will operate together with existing or testbed versions of new subsystems and components and to devise concepts of operation using the new and the legacy subsystems and components in the actual operational environment. When such a development process, part of what has been called spiral development, is used, new equipment and concepts can be incorporated into the fleet and the Marine forces based on validated concepts of operation.
Read the entire page →

Key Terms

  • power projection
  • forward presence
  • spiral development
  • naval force
  • marine corps

  • command levels
  • force elements
  • marine forces
  • coalition forces
  • projection mission

  • naval operations
  • legacy subsystems
  • marine units
  • operational concepts
  • development command

  • national agencies
  • major theater
  • validated concepts
  • mission assignment
  • joint actions

  • decentralized execution
  • current according
  • subsystems designed
  • targeting knowledge
  • force network

  • standard interfaces
  • dispersed sources
  • naval command
  • force units
  • encompass naval


    • 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.