• Military Menu                       

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

• WMD
• Intelligence
• Homeland Security
• Space

STATEMENT BY 
 DAVID TILLOTSON III, SES
DIRECTOR FOR C4ISR ARCHITECTURE AND ASSESSMENT
DEPUTY CHIEF OF STAFF, WARFIGHTING INTEGRATION
HEADQUARTERS UNITED STATES AIR FORCE

 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 AIR FORCE INFORMATION TECHNOLOGY ARCHITECTURE

FEBRUARY 11, 2004

Mr. Chairman and member of the subcommittee 

I am honored to be here today to discuss the Air Force's contribution to the Global Information Grid and net-centric warfare.  Let me first take this opportunity to thank you for your continued support of the men and women of our Armed Forces.  

A quick after-action review for Operations Iraqi Freedom (OIF) and Enduring Freedom (OEF) found that our Soldiers, Sailors, Airmen and Marines were more powerful and effective than ever before.  This effectiveness was seen in increased precision, speed and lethality.  As we become more effective, our adversaries have become keenly aware of the reaction time for our operators to obtain information and disseminate it to the shooters.  At times they are able to exploit any delay and adapt tactics to improve their survivability.  Just a few years ago, reaction time for time-critical targets was nominally measured in hours.  Although reaction time was compressed to double-digit minutes during OIF, it's clear that future operations will require reaction times in the single digits.  

To reach this goal we must achieve decision superiority and full-spectrum dominance in a Joint warfighting environment.  The DoD's fundamental approach toward these ends is to use the construct of the Global Information Grid (GIG) to aim at a net-centric force and operation.  In addition to the overarching GIG architecture and the DoD Architecture Framework, the Department outlines a combat systems construct (the Joint Task Force core architecture), a business construct (the Business Enterprise Architecture), and guidelines for the supporting IT infrastructure (the Network Centric Operations Reference Model and Joint Technical Architecture) which guide the development of processes and systems which the Air Force deploys.  I will focus in the remainder of this statement on the warfighting construct that appears to be the focus of this committee's discussions, but also note that the Air Force business enterprise also flows from the DoD business enterprise architecture in the same manner I will describe for the warfighting systems. 

The C2 Constellation as a Component of the GIG

The Air Force's contribution to the overarching concept for warfighting operations is the C2 Constellation, which are the USAF components to the GIG.  The C2 Constellation is a family of C4ISR systems sharing horizontally and vertically integrated information through machine-to-machine conversations enabled by a peer-based network of sensors, command centers and shooters.  It is an operational construct and architectural framework that guides our development of people, processes and technology toward network-centric operations and the achievement of decision superiority and air and space dominance in support of the Joint Forces Commander.  

Key elements of this C2 Constellation include the various platforms and sensors the USAF provides to the Joint Force Commander and key programs that support command centers such as the Air Operations Center and the Distributed Common Ground Segment (DCGS).  Underpinning programs within the AOC, such as the Theater Battle Management Core System (TBMCS) already serve as the joint standard for air operations planning and execution, and we are continuing to migrate these systems to a more modern, web-enabled architecture.  I will say more about the USAF effort on DCGS later, but will note here that it forms the basis for moving the entire DoD DCGS to a more modern, net-centric architecture.

In addition, the USAF provides transportation layer components of the overall DoD GIG under an effort we call ConstellationNet.  The ConstellationNet is the communications network-air, space, and terrestrial-that must allow a free flow of information so that it is rapidly accessible and presented to warfighters at the right time and right place to create the commander's desired effects.  GIG transport layer components delivered under this effort are included in various USAF programs.  The USAF portion of GIG-BE (GIG Bandwidth Expansion) provides expanded terrestrial service at key USAF bases globally.  The Joint Tactical Radio System (JTRS) is essential to our vision for an improved airborne network, which expands genuine network operations to the airborne platforms.  With the installation of Family of Advanced Beyond line of sight Terminals (FAB-T) on additional aircraft, such as AWACS, JSTARS and Global Hawk, we will have the capability to vastly extend our airborne network to all reaches of the globe.  Finally, the USAF is responsible for a large portion of the space segment communication evolution including deployment of the Advanced EHF, Wideband Gapfiller System and the Transformational Satellite (TSAT) program.  Each of these MILSATCOM systems represents progressive improvement in quality of service to all joint warfighters.  The TSAT program, in particular, extends the network to the space segment by providing high capacity, IP routing on the space segment and providing protected, high bandwidth access to air and surface forces on the move. 

Architecture, Standards and Defining the Path

In order to ensure that the goal of a DoD Global Information Grid is realized, the Air Force, like the other Services, are both contributing to and deriving planning from the architectural frameworks developed under the leadership of OSD(NII) and the Joint Staff.  Starting with these joint architecture frameworks, we apply the activity models and technical standards to the components of the DoD system for which the USAF is accountable.  In addition, we are engaged directly with our Sister Services in teaming together at the technical, working, policy and senior-leader levels to achieve network-centric operations.  These joint efforts are directed toward our desired end-state-completely integrated C4ISR.  Ongoing activities include a cross-service Architecture group led by OSD, the Joint Battle Management Command and Control (JBMC2) roadmap group, the Joint Battle Management C2 board of directors under Joint Forces Command lead, an Airborne Networking Cross-Service Senior Steering Group and multi-service groups at various levels.  The discussion among all these activities is facilitated and enabled by our ability to speak to common architectural components and standards, all of which are key to realizing interoperability.   All of this activity is keeping us firmly on the path to deployment of interoperable, net-centric systems that realize the vision of empowering the users through easy access to information anytime and anyplace, with attendant security.  Some examples highlight the case:

The USAF is integrating architecture products and process into its requirements reviews.  Stepping beyond the requirements of the Joint Staff process, the USAF is scrubbing its efforts in terms of a number of use cases that we call CONOPS focus us on key capabilities of the force.  Both the operational processes and the systems are cast in an architectural setting reflecting either an "as is" or "to be" condition as we assess how procedures, systems, and their associated investments contribute to needed capability. That architecture is key to focused analysis.  A similar process is underpinning the Joint Staff and other service activities.

Services are taking the architectural and standards guidance issued by the Department and applying it to shape decisions about programs and standards even at the service level.  Applying the data standards from the Department, the services developed and sent to the Joint Staff a message standard which transforms Link 16 messaging standard to Extensible Markup Language (XML).  Drawing from lessons learned in Cluster 1, and recognizing the benefits of common software and hardware components from architectural and engineering analysis, the Navy and USAF acquisition executives proposed combining the JTRS Cluster 3 and 4 development effort into one program.  This recommendation was endorsed by the Defense Acquisition Board (DAB) in Dec 03.  

Early discussion of architecture and network-centric requirements are driving early direction and management decisions for key programs at the Department level.  The USAF was faced with the need to recapitalize its aging DCGS system and crafted an approach which derived from the standards set by the GIG architecture and Network Centric Reference Model as the basis for a new requirement.  Subjected to service and DoD review, the approach proved attractive to all and the USAF program was adopted as developing the backbone for the broader DoD DCGS modernization effort.  The DAB directed the use of the integration backbone and multi-int fusion as the migration path for all the service DCGS elements.  As a result, the USAF RFP was modified to include other Service requirements, and all Services participate in the program oversight process.  The key was early development of an architectural foundation that addressed the key precepts of net-centric operations and conformance to the GIG architecture.

The USAF-led TSAT program is a key component of the GIG and its evolution.  TSAT requirements were derived from two years of architecture-based studies that from the outset cast the TSAT as a component of a joint, interagency network architecture.  Potential technical approaches balanced industry and commercial solutions with more specialized capability.  Designed as one element of a broader transformational communication architecture (TCA), the TSAT requirements were driven by consideration of all potential users and other network providers, but those requirements represent only a portion of the need.  Architecture allowed us to assess and allocate that requirement; standards ensure that the components will connect.  The TCA continues to guide the development and acquisition of TSAT and a number of other systems, and allows the Department to manage the consequences of changes across the other components of the architecture.  I led the Independent Program Assessment on TSAT, and we focused throughout the review on how the program office was establishing rigorous, architecture- and standards-based processes to ensure the synchronization of the TSAT program with other components of the architecture.  In addition, we explored how the other agencies and services would participate in this process.  The review of an AF program immediately led to interaction with the intelligence community, all the services, the Joint Staff, STRATCOM, and OSD.  The architecture and engineering forums in the Department and the GIG end-to-end testbed that have been established are key components of the development process that this program has embraced.  The common language that will unite this effort with the broader GIG is the architecture and standards handed down from the Department and implemented by the programs.   

Commitment to the Vision and the Basis for the Flight Ahead

The USAF fits as a component of the joint warfighting effort.  

Our systems reflect the same tenet - they are a component of the broader GIG.  The detailed architecture we develop flows directly from the standards set by the Department and provide a more detailed view of a component of that overall architecture.  

Architecture and standards provide a common mechanism for communication among the services and agencies.  We are adopting the reference model approach called out in the Federal Enterprise Architecture framework, ensuring these reflect the standards imposed by DoD, and extending the details to the USAF level.  These architectures and standards are becoming a regular part of our decision processes at all levels within the service, among the services and between the services and Joint Staff and OSD.  The architecture products we develop are provided back to other services, the DoD and Joint Staff and to industry to facilitate decisions and guide development.  

The USAF is committed to realizing a vision of providing a comprehensive information capability that is global, robust, survivable, interoperable, secure, and  reliable that allows warfighters to create the right effect, at the right time, at the right point in the battlespace.  Architectures and standards ensure we maintain course on that flight path.