. "4 Designing a Common Command and Information Infrastructure." Network-Centric Naval Forces: A Transition Strategy for Enhancing Operational Capabilities. Washington, DC: The National Academies Press, 2000.
The following HTML text is provided to enhance online
readability. Many aspects of typography translate only awkwardly to HTML.
Please use the page image
as the authoritative form to ensure accuracy.
Network-Centric Naval Forces: A Transition Strategy for Enhancing Operational Capabilities
areas. Of the three organizations, SPAWAR is the only one that has developed operational architectures, although these are primarily as-is architectures. Organizations from the doctrine and experimentation communities might be appropriate for developing the future operational architectures.
Organizational responsibility for the NCII architecture must be assigned before the architecture can be properly developed and implemented. The matter of organizational responsibility for network-centric operations as a whole, including NCII development and operation, is discussed in detail in Chapter 7. One suggested scheme for assigning responsibilities for the NCII in keeping with the discussion above and consistent with the material in Chapter 7, could be as follows:
Resource allocation and requirements sponsor: OPNAV N6;
Operational architecture: Commander, Operations Information and Space Command, with the support of OPNAV N6;
Policy and standards: Department of the Navy Chief Information Officer;
Systems and technical architectures (including enforcement): Department of the Navy Chief Engineer;
Acquisition and procurement: Program management as designated by the ASN (RDA) (e.g., the PEO-IT); and
Operational management: Commander, Operations Information and Space Command.
Included in this list is a new position introduced and recommended in Chapter 7—the Commander, Operations Information and Space Command. This individual would be a functional type commander analogous to existing type commanders (e.g., for air assets) and would be concerned with the information assets of the fleet just as the other type commanders are concerned with the assets in their areas. SPAWAR, NAVSEA, and NAVAIR would also figure in the assignment of responsibilities by providing support to the areas listed.23
The recommendations presented here are organized according to the three main topics discussed above: establishment of the NCII, tactical networks, and architecture development.
Chapter 7 also recommends double-hatting a Navy SYSCOM commander as a deputy to the ASN (RDA) for integration of network-centric operations. This individual would coordinate in the acquisition and procurement decisions.