FORCEnet Implementation Strategy (2005) / Chapter Skim
Currently Skimming:
5 FORCEnet Architecture and System Design
5 FORCEnet Architecture and System Design
Pages 115-141
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 115... ...
The design and implementation of complex systems for purposes of warfighting require a dedicated core of warfighters and system engineers trained in the art of operations analysis. Together, warfighters and engineers make decisions about when and how to introduce new capabilities as technologies and operational concepts evolve in independent but integrated spirals, as described in Chapter 2.
|
From page 116... ...
Initial TSAT operational capability is scheduled for 2012 or later, which seems out of sync with plans for near-term initial releases of horizontal data fusion and enterprise services as envisioned by the ASD(NII)
|
From page 117... ...
The FORCEnet security architecture work that is in progress is commendable and must continue with high priority throughout the design and implementation process. The security architecture must permeate FORCEnet end to end, from network access controls through applications access to data access within applications.
|
From page 118... ...
For example, a hub-and-spoke configuration with ad hoc networking could support near-term capability enhancements. Multiple hubs supported by an airborne relay could provide needed redundancy, while allowing limited satellite bandwidth to be shared between assets within a 200 mile radius of the relay.
|
From page 119... ...
Net-Centric Checklist and validated with performance modeling and sensitivity analysis, would provide a solid foundation for the FORCEnet information architecture. The network control system could then be designed to route and throttle information across the boundaries on the basis of mission priorities and available capacity and capability.
|
From page 120... ...
Ten years later, IP became the architectural definition. An example of an effective process is one called user-centered design, in which desired functionality is defined in terms of "use cases." The Navy sometimes calls these use cases Design Reference Missions, and the joint community calls them mission threads.
|
From page 121... ...
The output of the FORCEnet Baseline Process, briefed to the FORCEnet EXCOMM on June 23, 2004, will undoubtedly modify the list as systems are placed in compliance categories. 4Space and Naval Warfare Systems Command.
|
From page 122... ...
In addition, a dozen IT service categories have been defined: networking, identity management, security, operating system, user (person) -to-computer interface, data management, data interchange, multimedia/ 5 Space and Naval Warfare Systems Command.
|
From page 123... ...
A service component is made up of standards, interfaces, protocols, and product specifications. Examples of possible service components by service category include the following: · Networking: network management, address management, and routing protocols; · Identity management: federated directory service; · Security: identification, authentication, audit trail creation and analysis, access controls, cryptography management, virus protection, intrusion prevention and detection; · Operating system: kernel operations, fault management, utilities, backup and recovery; · User (person)
|
From page 124... ...
Almost 300 standards are mandated in Volume II. They cover such areas as data formats; operating system services; sensor interfaces; position, navigation, and time; information assurance; and information transfer.
|
From page 125... ...
The checklist is a fairly demanding document, containing perhaps a hundred or more questions, each of which will require some thoughtful effort to answer. Typical questions are, "Describe how the visible data assets are made available to other users outside the Community of Interest with a need for the data" and "Does the service offering depend on or use any other services provided by a different program or service provider -- if so, explain how this works."7 The NII checklist covers a wide variety of topics, ranging from questions such as the example given above about how data will be made available to external applications, through scalability of services, to specifics of information assurance and datagram transport.
|
From page 126... ...
Net-Centric Checklist and the FORCEnet Compliance Checklist FORCEnet Compliance Category NII Net-Centric Checklist Checklist Data Visibility, sharability, discoverability, schemas, List of format standards, security of, pedigree, integrity, design patterns, data modeling metadata, standards, evolution, user feedback Service Open architecture, scalability of load and users, Time, resource locator, operations during outage, operations over variable video conferencing bandwidth, observability of state and performance, data formats, file transfer Information Identity management, security across domains, Password, encryption, assurance/ detection and response to attacks and anomalies human security security Transport Internet Protocol Version 6, multiple data (voice, Transport protocols, file video, data) on single network, quality of service, transfer, Internet Protocol radio, fault management, detection, correction, fault isolation, diagnosis, correction, problem tracking Other Documentation contains specific constructs, addresses certain issues
|
From page 127... ...
The open architecture functional architecture shown in Figure 5.2, coupled with the FORCEnet information architecture described above, will, when implemented, greatly simplify the implementation of FORCEnet. 5.3.5 FORCEnet Executive Committee On February 19, 2004, the ASN(RDA)
|
From page 128... ...
128 RV, ex time; direct real near DX/DR, NRT, control; communications; and architecture. open satellite command OA, C2, SatCom, group; battle intelligence; Committee; BG, area; INTEL, Executive NOTES: operating EXCOMM, common architecture.
|
From page 129... ...
The decisions went beyond those reflected in the SPAWAR FORCEnet Business Strategy Version 1.0 and expanded the number and scope of FORCEnet pilot programs. Near-term pilots for the Marine Corps, the DCGS, and the JFN were added, and a decision was made to reallocate funds to support FORCEnet implementation.
|
From page 130... ...
It is already known that some of the interfaces that must be controlled are internal to ongoing acquisition programs and directly impact the architecture of the software and hardware that comprise these programs. In effect, some existing systems could be torn apart and their functionality rearchitected to support horizontal
|
From page 131... ...
A construct for the way that change will be managed for FORCEnet functional partitions and standards in the context of the GIG and joint force must be developed in concert with the FORCEnet designated approval authority. 5.5 MANAGEMENT OF OPERATIONS It is expected that one or more control facilities will be required to manage the performance of the FORCEnet infrastructure.
|
From page 132... ...
Other data sharing, as for collaborative sensor networks, may not require that every data message be received -- User Datagram Protocol, for example, may be the appropriate IP in this case. 5.5.2 Recommended Metrics for Warfighting Effectiveness The following three interoperability metrics for the antiair-warfare area are an example of those recommended for measurement of the warfighting effectiveness of FORCEnet.
|
From page 133... ...
. If a FORCEnet capability does not improve battle force reaction time, it should not be deployed.
|
From page 134... ...
Increasing numbers of such events in the late 1990s resulted in the establishment by the Naval Sea Systems Command (NAVSEA) of a DEP and a battle-groupspecific deployment-minus-30-month countdown configuration management and test process for combat and C4I systems planned for deployment.
|
From page 135... ...
FORCENET ARCHITECTURE AND SYSTEM DESIGN 135 cycles of joint and Service-specific systems in a joint setting. However, the definition and focus of the JDEP have been slow in realization of their intended capabilities.
|
From page 136... ...
The committee notes that information assurance policies and technologies provide protection against risk at some cost (burden) , in terms of both efficiency and restrictions on operator activities.
|
From page 137... ...
Telephone call centers from Maryland to New Jersey lost service for half a day. Although the Navy and Marine Corps do not currently appear to be particularly vulnerable to such catastrophes, it does not take too much imagination to picture how such cascading failures might affect the Navy once all naval platforms are networked.
|
From page 138... ...
5.8 FINDINGS AND RECOMMENDATIONS 5.8.1 Findings Following are the findings and observations of the committee with respect to FORCEnet architecture and system design: · The process and tools for translating FORCEnet operational concepts into products, services, and warfighting capabilities have yet to be fully developed. Systems engineering is a process for allocating functionality to subsystems that are bounded by a system architecture.
|
From page 139... ...
· Recommendation for OPNAV: Adopt the Net-Centric Checklist of the ASD(NII) in place of the OPNAV FORCEnet Compliance Checklist, adapting it
|
From page 140... ...
The decisions of this authority will affect a broad range of naval programs, unprecedented in any prior DOD systems engineering. This authority is key to maintaining the integrity of overall FORCEnet capabilities.
|
From page 141... ...
: Invite the fleet community to provide a senior flag officer to participate in the FORCEnet EXCOMM decision process.
|
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.