• Military Menu                       

• Introduction
• Systems
• Facilities
• Agencies
• Industry
• Operations
• Countries
• Hot Documents
• News
• Reports
• Policy
• Budget
• Congress
• Links

• WMD
• Intelligence
• Homeland Security
• Space

STATEMENT BY 
 RADM THOMAS E. ZELIBOR, USN
DEPUTY FOR C4 INTEGRATION AND POLICY
DEPARTMENT OF NAVY DEPUTY CIO FOR NAVY 

 BEFORE THE
COMMITTEE ON ARMED SERVICES
SUBCOMMITTEE ON TERRORISM, UNCONVENTIONAL THREATS AND CAPABILITIES
UNITED STATES HOUSE OF REPRESENTATIVES

REGARDING DEPARTMENT OF DEFENSE INFORMATION SYSTEMS ARCHITECTURE: ARE WE ON THE RIGHT PATH TO ACHIEVING NET - CENTRICITY AND ENSURING INTEROPERABILITY?
US NAVY INFORMATION TECHNOLOGY (IT) ARCHITECTURE: FORCENET

FEBRUARY 11, 2004

 

 Introduction

Mr. Chairman and distinguished members of the Terrorism, Unconventional Threats and Capabilities Subcommittee, thank you for this opportunity to appear before the committee to discuss the Navy's Information Technology (IT) architecture framework, called FORCEnet, and how we are interfacing with the Department's Global Information Grid (GIG) initiatives as well as the other Services' and Federal IT architectures.

Background

What is FORCEnet?

FORCEnet is the Navy and Marine Corps' means of operationalizing the concepts of network centric warfare.  Within Sea Power 21, the Chief of Naval Operations defines FORCEnet as the operational construct and architectural framework for naval warfare in the Information Age that integrates warriors, sensors, networks, command and control, platforms and weapons into a networked, distributed combat force, scalable across the spectrum of conflict from seabed to space and sea to land.  FORCEnet is not a program, but the forcing function for organizing, planning and investing in Navy's IT and tactical information architecture.  The Department of Defense (DoD) and the other Services are working towards the same end-state.  Under the leadership of Assistant Secretary of Defense for Network and Information Integration (ASD (NII)), the Services and Agencies are working together to develop a consistent set of information technology policies, strategies, architectures and standards across the DoD.  

Architecture

Instead of developing our own architectures and standards from the ground up, Navy is participating fully in the DOD's architecture and standards development process to ensure Navy improves interoperability amongst joint forces.  For example, at the OSD level, Navy participates in the Assistant Secretary of Defense for Network and Information Integration (ASD (NII)) Global Information Grid (GIG) Architecture development; and at the joint level, Navy participates in the Joint Forces Command (JFCOM) chartered Cross-Service Architecture Integration Working Group.  Within the construct of a Joint Task Force, the JFCOM working group defines and develops the Joint Command and Control (JC2) architecture for DOD.  Thus, the FORCEnet architecture is based on GIG architecture development, and is the Navy's instantiation for implementing seamless integration across multiple domains.   

The GIG Architecture is "a globally interconnected end-to-end set of information capabilities, associated processes, and personnel for collecting, processing, storing, disseminating, and managing information on demand to warfighters, policy makers, and support personnel."  The GIG has become the organizing construct for achieving net-centric operations and warfare across the DOD.  The GIG includes both warfighting and business domains.  Likewise, we are working to integrate our tactical and warfighter support domains in an overarching Department of Navy Enterprise Architecture, of which FORCEnet is a key component.

Navy is strongly engaged in and influencing the development of key GIG Architecture components so that we can leverage "born joint" architectures.  For example, Navy fully participates in the development of  (a) Transformational Communications Architecture (TCA), transforming future satellite communications; (b) the Global Information Grid - Bandwidth Expansion (GIG-BE), bringing high data rate connectivity to worldwide bases and facilities; (c)Teleports , that connects current and future satellite communications architectures and terrestrial networks; (d)Joint Tactical Radio System (JTRS) that will  provide a family of interoperable radios to enable joint tactical communications; (e) GIG Enterprise Services (GES)/Net-Centric Enterprise Services (NCES) that brings an enterprise perspective to DOD application and information handling processes; (f) Information Assurance (IA) initiatives, providing secure interoperable networks; and (g) Internet Protocol Version 6 implementation, that will provide added security and quality of service for our communications.

Challenges

Maintaining legacy architectures while defining future architectures and then investing to migrate to those future architectures is the major challenge.  The Navy's challenge continues to be synchronizing the integration of our existing systems into joint architectures while ensuring we remain connected to our allies and coalition partners as well as Homeland Security Agencies, such as the Coast Guard.    For example, Navy is working the migration of our legacy satellite communications (SATCOM) systems into the Transformational Communications Architecture (TCA) for satellite communications.  Navy fully participates in TCA development and will leverage TCA based systems to meet our forecasted SATCOM needs.  Our requirements were consolidated with other Services and intelligence agencies to ensure there is a joint perspective on future satellite communications services.  The process to achieve this architecture works well and the TCA represents a DoD, Intelligence Community and NASA approved satellite communications architecture.  This joint approach is a first in the satellite communications business.     

We are exploring the integration of tactical and non-tactical networks as we take a holistic perspective on optimizing warfighting capabilities.  Afloat and ashore IT architectures must be seamlessly integrated and interfaced so that units transiting from East or West Coast ports to overseas locations can operate jointly.  We are in the process of developing an integrated roadmap for both tactical and non-tactical networks such as our overseas Base Level Information Infrastructure (BLII), our CONUS based Navy Marine Corps Intranet (NMCI), and our afloat networks. Perhaps a simple analogy might serve to illustrate the Navy's role in GIG Architecture development.  GIG initiatives like the GIG-Bandwidth Expansion could be viewed as the National Interstate Highway System.  The Federal Government builds the Interstate Highway System in coordination with the States, while the States build roads that connect to the Interstate Highway System. All users of this highway system employ the same traffic signals and signs for interoperability.   FORCEnet builds "Navy" roads to the "GIG" interstate, using common standards for interoperability such as the Joint Technical Architecture (JTA).  Additionally, we use and enforce a FORCEnet Compliance Checklist to ensure that all Navy programs are FORCEnet and GIG-compliant.

Experimentation, demonstration and testing are also important activities for determining architecture development and Navy is conducting a series of operational demonstrations called Trident Warrior in coordination with the other Services.  These operational demonstrations help in the accelerated innovation, assessment, and fielding of warfighter capability.  Navy is hosting the ASD (NII)-sponsored Global Information Grid/Transformational Communications (GIG/TC) Testbed at the Navy Research Lab (NRL).  The GIG/TC Testbed will connect the FORCEnet Testbed with other Service and Agency testbeds for the purpose of conducting end-to-end testing on all GIG-compliant systems as those systems are developed.

Summary

In summary, Navy remains heavily engaged with ASD (NII) and the other Services and Agencies in creating a joint, interoperable GIG Architecture.   Through agreed upon standards and business processes, we are breaking down traditional stovepipe approaches and working towards achieving joint and coalition interoperability.  Furthermore, we are migrating towards enterprise solutions across the Navy and the DoD to deliver information to the warfighter.  With your continued strong support, our military has made significant progress improving our joint warfighting and business capabilities, and transforming our military into a 21^st Century fighting force.  We appreciate your efforts to help us be responsive to a changing world, and in supporting the warfighters that make the world a safer and better place.  Thank you for this opportunity to address the committee on this important issue.