Skip to main content

Currently Skimming:

5 Computers
Pages 132-150

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 132...
... applications to fit the revised work flow in which a naval strike group is engaging. · The ability to insert available new technology that could help to adjust existing operational capabilities so as to better match the specific activities of adversaries and the current objectives of U.S.
From page 133...
... The achievement of composability and adaptability requires interoperability, but in a form that goes beyond currently envisioned interoperability initiatives. 5.1 COMPOSABILITY AND ARCHITECTURE A major objective of the new naval strike group construct is the ability to assemble and employ tailored capability packages to make optimum use of limited resources in circumstances involving simultaneous, ambiguous, and dynamic operational contingencies.
From page 134...
... Overlays permit logical connections between software applications designed to exchange information that needs to occur transparently across a diverse set of networks (e.g., Internet Protocol, version 6 [IPv6]
From page 135...
... COMPUTERS 135 composability and adaptability objectives, and on the pursuit of open standards to support implementations. As indicated in Chapters 3 and 4, the Department of Defense (DOD)
From page 136...
... · The DOD will be building some of the largest-scale SOAs developed to date. However, best practices will need to be developed for enhancing the scalability properties of these architectures for larger and larger applications involving larger numbers of users, sensors, and software applications with respect to bandwidth, network management, information caching and replication, and other such metrics.
From page 137...
... COMPUTERS 137 SOA scheme of things (number of users, number of uses, criticality of uses, and so on)
From page 138...
... This is particularly true for Navy-specific C4ISR systems (e.g., undersea warfare [USW] systems)
From page 139...
... for the development of the critical work flows developed to support Army and Marine Corps systems in preparation for Operation Iraqi Freedom. Despite 6 months to prepare, some work flows were unachievable, particularly those requiring interoperability between Army and Marine Expeditionary Unit (MEU)
From page 140...
... 140 C4ISR FOR FUTURE NAVAL STRIKE GROUPS l Twelve critical workflows identified OPERATIONS INTELLIGENCE by CFLCC to share information across force components CFLCC Cross-Service/Echelon/Function C2PC Involving 36 major C2 systems C2PC GCCS-A ASAS-L ASAS Required 6 month rapid integration effort by Army CTSF and CERDEC V Corps Results still included "swivel chair" interoperability and other brittle C2PC GCCS-A ASAS-L ASAS hardwiring Some workflows not possible due 3ID to interoperability barriers (e.g., between Army and MEU C2 C2PC GCCS-A ASAS-L ASAS systems) l COP development and dissemination (Thread 3)
From page 141...
... Some amount of adaptability, especially within system subcomponents, is likely to be available in practice by that date. However, a semiautomated, human-in-the-loop ability to configure systems rapidly on the basis of the composable systems practices discussed above will allow Navy strike groups to have significantly greater flexibility than they have now to perform new and rapidly changing missions, especially in littoral or combined open-ocean and littoral operations.
From page 142...
... 142 C4ISR FOR FUTURE NAVAL STRIKE GROUPS · Navy assets will be part of configurations established by others. The Navy should assure itself that these configurations are suitably protected relative to normal Navy uses.
From page 143...
... COMPUTERS 143 can develop information exchanges with significantly less, and eventually no, human interaction. An ontology defines the terms used to describe and represent an area of knowledge.
From page 144...
... 144 C4ISR FOR FUTURE NAVAL STRIKE GROUPS requirements. For a predetermined arrangement of software and hardware components, it is possible to evaluate response times versus performance needs, and the portion of the time budget allocated to communications.
From page 145...
... COMPUTERS 145 service-oriented or composable architecture, the Navy needs to assign new efforts to be carried out by its development community, its research community, its operational community, and its system support community. 5.6.1 Development Currently, the Navy will typically initiate the development of a new C4ISR system (for the purposes of this report, a new subsystem, to become a part of a broad array of C4ISR subsystems to be integrated as an overall system, i.e., a system within a system-of-systems)
From page 146...
... 90; and in National Research Council, 2004, The Role of Experimentation in Building Future Naval Forces, The National Academies Press, Washington, D.C., p.
From page 147...
... COMPUTERS 147 5.6.2 Research While the Navy development community is not yet organized to fully incorporate SOAs and CAs, certain Navy-funded research efforts have started to develop concepts for these architectures (see Chapter 4, Section 4.6)
From page 148...
... 148 C4ISR FOR FUTURE NAVAL STRIKE GROUPS diate needs. In order to perform these tasks quickly, a specialized support capability will be required that can deal with the full system of systems.
From page 149...
... Team (HURT) Program, researchers are developing a system using model-based control algorithms to control a set of unmanned aerial vehicles (UAVs)
From page 150...
... 150 C4ISR FOR FUTURE NAVAL STRIKE GROUPS Finding: Current Navy procurement models for computer "systems" bundle hardware, software, and applications. This approach will not be appropriate for meeting composability needs.


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.