C4ISR for Future Naval Strike Groups (2006) / Chapter Skim
Currently Skimming:
3 Architecting and Building the Naval C4ISR System
3 Architecting and Building the Naval C4ISR System
Pages 70-103
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 70... ...
Section 3.3 then reviews the ongoing architecting activities of the Naval Services. Section 3.4 focuses on the need for authoritative Department of the Navy architectural guidance and on mechanisms for translating this guidance into fielded capabilities.
|
From page 71... ...
NOTE: The local area networks, shown on the right as four clouds, may or may not have routers and communication paths distinct from the Global Information Grid. SOURCE: Adapted, with permission, from C.J.
|
From page 72... ...
3.2.1 The Network-Centric Vision The Global Information Grid For the broadly defined information architecture, the Global Information Grid (GIG) 1 and its attributes are essential.
|
From page 73... ...
· Transformational Satellite (TSAT) -- Worldwide robust SATCOM -- Laser communications for crosslinks and reach-back TSAT 2013 -- Wideband radio-frequency links also available · Network Centric Enterprise Services (NCES)
|
From page 74... ...
in the Joint Tactical Radio System (JTRS) will be available to form networks to extend the communications from TSAT terminals to the surrounding area, supporting tactical enclaves.
|
From page 75... ...
If the equivalent of today's "smart push" is demanded by latency or other considerations, this would be implemented through a publish-andsubscribe agreement with a value-added service provider. 3.3 IMPLICATIONS OF NETWORK-CENTRIC ARCHITECTURES FOR THE DEPARTMENT OF THE NAVY The achievement of a network-centric capability requires much more than the development of a short list of communications programs.
|
From page 76... ...
For example, by the end of 2005, the fiber-based core GIG network will be operational, with very few applications to exploit its full capability. Should not the Department of the Navy be working to install systems at fleet command centers that would dramatically change how imagery information flows from the NGA to the user?
|
From page 77... ...
Trade-offs will sometimes be required to achieve the low latencies needed for fast tactical response, as Chapter 2 addressed in its discussion of mission-cycle time. This point is also addressed in the companion Naval Studies Board (NSB)
|
From page 78... ...
78 C4ISR FOR FUTURE NAVAL STRIKE GROUPS Is the system using IA equipment from the High Assurance Internet Protocol Encryption (HAIPE) family?
|
From page 79... ...
With this discussion as a foundation, the sections below develop findings and recommendations regarding the further development of architectural guidance and the establishment of strengthened technical and management mechanisms to translate this guidance into fielded capability.
|
From page 80... ...
However, it is not clear to the committee that the Department of the Navy has implemented a successful capabilities-based approach to acquisition management -- one based on clear and consistent architectural principles with enforceable, consistent guidance and one that exercises trade-offs that are horizontal, crossing program boundaries. Rather, the required building blocks are being developed and fielded in the vertical world of programs, with overarching guidance being issued from multiple sources, although there are some convergence efforts attempting to deal with this problem, such as that of the Program Executive Office for Integrated Warfare Systems (PEO/IWS)
|
From page 82... ...
with the development of an open architecture (OA) 8 to facilitate the evolution of computing environments through 7Dennis Bauman, Program Executive Office for Command, Control, Communications, Computers, Intelligence, and Space.
|
From page 83... ...
The recent Naval Studies Board report entitled FORCEnet Implementation Strategy recommended these OA features as particularly relevant for FORCEnet because they facilitate the engineering of complex systems and their evolution over time.9 While OA has been described as being applicable to the central elements of FORCEnet as well as to computing environments within platforms, it is not clear that the applicability, relationship, or the attendant compliance responsibilities are well understood or accepted within the Navy. Nor does it appear to be fully understood how they relate to other guidance, such as standards designated by the Space and Naval Warfare Systems Command (SPAWAR)
|
From page 84... ...
, with its user-/fleet-driven charter and responsibilities for moving FORCEnet forward. · The assignment of FORCEnet system and technically oriented responsibilities to SPAWAR, including the designation of SPAWAR as the FORCEnet Chief Engineer and the assignment to SPAWAR of responsibility for assessing programs vis-à-vis FORCEnet objectives.
|
From page 85... ...
SPAWAR is developing both system and technical architectures for FORCEnet in conjunction with the MCSC, and the FORCEnet Chief Engineer is in SPAWAR. Presentations to the committee indicated an almost exclusive emphasis on the FORCEnet enabling information infrastructure, with a seemingly protracted schedule for addressing the crucial topic of mission threads.
|
From page 86... ...
The committee shares the concerns of a predecessor Naval Studies Board committee that addressed itself specifically to a review of the FORCEnet implementation strategy. That NSB study delineated three components of FORCEnet: 1.
|
From page 87... ...
For example, under the network-centric paradigm, targeting latencies are strongly influenced by end-to-end performance of the common infrastructure. The current focus on enabling the information infrastructure is appropriate in that these capabilities provide the foundation of the C4ISR architecture.
|
From page 88... ...
3.5.1 Architectural Guidance The committee has emphasized the need for architectural imperatives for network-centricity that are accepted across all activities of the Naval Services and are implemented in a consistent fashion. The Department of the Navy should not only take ownership of these principles but also should lead the evolution of guidelines and standards that are most important to its problems.
|
From page 89... ...
What specific guidance regarding data handling and fusion would obviate the problems often experienced today with the common operational picture? It should be noted that such gaps in guidance are not unique to the Naval Services.
|
From page 90... ...
2002. The Navy Distributed Engineering Plant -- Value Added for the Fleet, Report Number A900004, Naval Surface Warfare Center, Dahlgren Division, Virginia, February 26.
|
From page 91... ...
. However, the current FORCEnet system engineering activities are distributed among multiple participants despite the central role of the SPAWAR FORCEnet CHENG.
|
From page 92... ...
that the Navy establish a senior Navy Chief Engineer position and a Marine Corps counterpart, reporting directly to their respective Service chiefs. It is understood that such a recommendation poses a number of institutional and organizational issues.
|
From page 93... ...
Placing this responsibility on the CNO/CMC staff puts the CHENG in the most effective place to ensure that architectural direction is supported by POR requirements and program-sponsor resource allocations. · Considerations both of emphasizing operational mission support and of compatibility with the Goldwater-Nichols acquisition structure favor positioning the recommended Chief Engineers as reporting directly to their Service chiefs.
|
From page 94... ...
As another example, an initiative to enhance machine-to-machine targeting time lines by simply introducing Extensible Mark-up Language (XML) -coded flows of selected targeting information was described in the Sea Trial presenta 15 Andrew Cox, Executive Director, Program Executive Office for Command, Control, Communications, Computer, and Space, "Information Brief to the Naval Studies Board," presentation to the committee, September 21, 2004, Slide #8.
|
From page 95... ...
95 , F, m; to User SLEP NA Execu- tion Mobile nformationI Wavefor System; service; presenta of Program Global MUOS, Network Board," quality Director, GIG-BE, 3 3 14 Wideband Studies FY Communications Block Frequency; Level Executive 13 NCES Naval FY High Protocol; System Cox, Functions Satellite the 1 12 100% to FY telecommunications Control Radio GIG Spiral Internet 11 Brief Policy WNW 2.0 Defense Extremely IP, Andrew Life QoS, FY and of Integrated 2 6; HAIPE 2 Tactical End TC 10 Block 75% DSCS, FY Functions, Level DSCS NCES Joint version Terminals Advanced SOURCE: 09 Access "Information TC FY NOTE: Encryption; Network WNW, 08 IPv6 Fielding IPv6 50% AEHF, FY Control. 100% Start Space, 1 Protocol, 100% Service, 1 and 1.0 of Surrogate JTRS 07 Block Networks and Network Level FY IPv6 Protocol WNW IP HAIPE Quality to System; NCES opportunities.
|
From page 96... ...
3.5.4 Summary of Architectural and Implementation Findings and Recommendations The findings and recommendations of this chapter are presented below. Finding: A C4ISR architecture for future naval strike groups should exploit the communications and information-management capabilities of the DOD's Global Information Grid (GIG)
|
From page 97... ...
As is acknowledged in Figure 3.5, however, certain legacy and specialpurposes systems, as well as those with limited bandwidth connectivity to the GIG, will be connected to the GIG via gateways. The ISR architecture should have platforms and sensors networked and layered and operated as part of the Naval Services' major missions (e.g., Strike, 17The section on "Implementation Imperatives and Major Recommendations" in the Executive Summary of FORCEnet Implementation Strategy includes as a guiding principle to "exploit GIG capabilities while preparing to fill GIG gaps and determining the limits of network centricity." See National Research Council, 2005, FORCEnet Implementation Strategy, The National Academies Press, Washington, D.C., p.
|
From page 98... ...
98 ervicesS GIG } Infrastructure NOTE: applicable. NCES where Layers approach Transport to service-oriented Presentation using Physical 2 Orchestration systems, Logic Mediation Node Data Communications, Presentation Discovery come.
|
From page 99... ...
Steps are being taken to address these issues, but there still appear to be organizational stovepipes to be overcome, as well as a need for selective clarification of the organizational scope and responsibility. Similar issues exist relative to applying architectural guidance from external communities with which the naval architectures must interface -- especially the Office of the Secretary of Defense's Global Information Grid (GIG)
|
From page 100... ...
The Navy Chief Engineer and his or her Marine Corps counterpart should be supported by a robust, enterprise-wide mission systems engineering and experimentation activity to guide and shape major component programs toward the objective of achieving full network-centric C4ISR system-of-systems capability.
|
From page 101... ...
The Navy Chief Engineer and his or her Marine Corps counterpart must be informed regarding matters involving technical, cost, schedule, and risk issues as a basis for their guidance and influence -- thus the need for a robust, dedicated system engineering activity building on related ongoing activities. · Augment engineering, modeling, testing, and integration strategies, tools, and facilities to ensure system-of-systems design integrity and to place realistic bounds on end-to-end performance.
|
From page 102... ...
Doing so would also position the Navy to satisfy its requirements in a way that meets joint Service capability needs. The near-term planning and analysis activity conducted by the Navy Chief Engineer and his or her Marine Corps counterpart should accelerate the network 19Andrew Cox, Executive Director, Program Executive Office for C4I and Space, "Information Brief to the Naval Studies Board," presentation to the committee, September 21, 2004.
|
From page 103... ...
· Design and develop those COI services, using a spiral development and acquisition program to achieve executable architectures. · Build a spiral acquisition program for these COI services using modeling and simulation akin to the Navy Distributed Engineering Plant and Sea Trial experimentation to help validate the iterative evolution of these services.
|
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.