JITC Mission Brief to the MCEB

1. 1 JITC Mission Brief to the MCEB Richard A. Meador JITC (Fort Huachuca, AZ) DSN 879-5009 Meadorr@fhu.disa.mil 10 February 2003 Good morning. I�m Rick Meador from the Joint Interoperability Test Command. I�m located at Fort Huachuca, AZ, but I also wanted to provide you with contact information from our division and test facilities here in the NCR. Mr. Mike Mangan heads up our East Coast operations, and like I, he would be glad to address any questions you have about JITC and to invite you to visit either our AZ or MD locations. Good morning. I�m Rick Meador from the Joint Interoperability Test Command. I�m located at Fort Huachuca, AZ, but I also wanted to provide you with contact information from our division and test facilities here in the NCR. Mr. Mike Mangan heads up our East Coast operations, and like I, he would be glad to address any questions you have about JITC and to invite you to visit either our AZ or MD locations.

2. 2 Purpose and Background This brief provides an overview of the JITC. It is for information purposes only. Since 2000, JITC has provided semi-annual briefs to the MCEB to highlight the interoperability status of given functional areas such as tactical and strategic communications, command and control over the Joint Data Network, intelligence, and combined interoperability. Indeed, this month, we briefed the MCEB coordinators concerning interoperability within the logistics functional area. After our last interoperability update, in August of 2002, the MCEB Principals requested a broader level briefing about the JITC. This is the response to that request. This brief provides an overview of the JITC. It is for information purposes only. Since 2000, JITC has provided semi-annual briefs to the MCEB to highlight the interoperability status of given functional areas such as tactical and strategic communications, command and control over the Joint Data Network, intelligence, and combined interoperability. Indeed, this month, we briefed the MCEB coordinators concerning interoperability within the logistics functional area. After our last interoperability update, in August of 2002, the MCEB Principals requested a broader level briefing about the JITC. This is the response to that request.

3. 3 Importance of Interoperability Sir, I know that you and the other members of the MCEB understand the importance of interoperability. But I wanted to start with a couple of examples to set the stage. The first picture, which you are about to see, is taken from an interoperability test JITC conducted with the services and agencies in support of the Missile Defense Agency. This portion of the test involved two enemy missiles coming from approximately the same launch point but targeting two different friendly assets. Various missile defense systems detect these missiles and begin to report on them. Thus, what you should see is something that resembles the McDonald�s arches. Instead, here�s what we found (click mouse; explain the problems). This next example is from an imagery test we did at Fort Huachuca. (Click the mouse.) The picture you see is what an intel analyst viewed on his system after retrieving two files from a library: one file is the image itself and another is associated annotations � in this case a target marker. As you can see, the analyst can read both the image and the annotations clearly even though they were developed and stored by a completely different system. (Click Mouse.) The problem is, here are the files that were actually stored. These examples highlight a critical aspect within DoD�s definition of interoperability: it requires more than passing data or even information � interoperability must allow participants to operate effectively together. In these cases, systems are indeed exchanging information � but they aren�t operating together effectively. Note that in the first example, the operators will know there are problems since missiles don�t fly in zig-zags. But whether they can sort through the confusion in time to successfully defend is a question we�d rather not answer in actual operations. In the second example, the operator has no clue that he has a problem. These are just two of many examples (others include 10-minute COP delay and false busy signals for telephone calls) which point out the importance of disciplined and detailed testing. That�s the role of JITC.Sir, I know that you and the other members of the MCEB understand the importance of interoperability. But I wanted to start with a couple of examples to set the stage. The first picture, which you are about to see, is taken from an interoperability test JITC conducted with the services and agencies in support of the Missile Defense Agency. This portion of the test involved two enemy missiles coming from approximately the same launch point but targeting two different friendly assets. Various missile defense systems detect these missiles and begin to report on them. Thus, what you should see is something that resembles the McDonald�s arches. Instead, here�s what we found (click mouse; explain the problems). This next example is from an imagery test we did at Fort Huachuca. (Click the mouse.) The picture you see is what an intel analyst viewed on his system after retrieving two files from a library: one file is the image itself and another is associated annotations � in this case a target marker. As you can see, the analyst can read both the image and the annotations clearly even though they were developed and stored by a completely different system. (Click Mouse.) The problem is, here are the files that were actually stored. These examples highlight a critical aspect within DoD�s definition of interoperability: it requires more than passing data or even information � interoperability must allow participants to operate effectively together. In these cases, systems are indeed exchanging information � but they aren�t operating together effectively. Note that in the first example, the operators will know there are problems since missiles don�t fly in zig-zags. But whether they can sort through the confusion in time to successfully defend is a question we�d rather not answer in actual operations. In the second example, the operator has no clue that he has a problem. These are just two of many examples (others include 10-minute COP delay and false busy signals for telephone calls) which point out the importance of disciplined and detailed testing. That�s the role of JITC.

4. 4 JITC�s Unique Roles Sole certifier for joint interoperability in DoD. Doesn�t mean we�re the only tester � isn�t possible. But through collaboration with users, testers, and developers, we get the necessary information and determine whether the system deserves certification � in other words, that the system meets the joint warfighters needs. Only non-service Operational Test Agency (4 other OTAs in DoD: ATEC, AFOTEC, COMOPTEVFOR, and MCOTEA). Report on operational suitability and effectiveness (beyond interoperability) for systems developed by DISA, DFAS, and other DoD Agencies. We also have MOAs with AFOTEC and MCOTEA in place and pending with ATEC and COMOPTEVFOR. These MOAs help insure efficient and effective interoperability evaluations through shared test data, facilities, and expertise. Only non-service member of the Major Range and Test Facility Base (20 others in DoD � all service owned). Allows us to work with industry, seeing their new products and helping them build in joint interoperability. Combination of these unique roles and the expertise we build up leads other agencies to select us to serve as their executive agent for testing. For example, as executive agent for NIMA, JITC tests imagery systems and maintains a registry of all that conform to transmission format standards. Commercial systems that want to be considered for DoD purchase can thus come through JITC and prove they meet the applicable standards. This is one of the best ways to insure systems are born joint: make industry develop components that conform to interoperability standards before they ever enter the DoD inventory. Finally, we go well beyond the traditional test role and provide direct interoperability advice and troubleshooting to warfighters in the field. Sole certifier for joint interoperability in DoD. Doesn�t mean we�re the only tester � isn�t possible. But through collaboration with users, testers, and developers, we get the necessary information and determine whether the system deserves certification � in other words, that the system meets the joint warfighters needs. Only non-service Operational Test Agency (4 other OTAs in DoD: ATEC, AFOTEC, COMOPTEVFOR, and MCOTEA). Report on operational suitability and effectiveness (beyond interoperability) for systems developed by DISA, DFAS, and other DoD Agencies. We also have MOAs with AFOTEC and MCOTEA in place and pending with ATEC and COMOPTEVFOR. These MOAs help insure efficient and effective interoperability evaluations through shared test data, facilities, and expertise. Only non-service member of the Major Range and Test Facility Base (20 others in DoD � all service owned). Allows us to work with industry, seeing their new products and helping them build in joint interoperability. Combination of these unique roles and the expertise we build up leads other agencies to select us to serve as their executive agent for testing. For example, as executive agent for NIMA, JITC tests imagery systems and maintains a registry of all that conform to transmission format standards. Commercial systems that want to be considered for DoD purchase can thus come through JITC and prove they meet the applicable standards. This is one of the best ways to insure systems are born joint: make industry develop components that conform to interoperability standards before they ever enter the DoD inventory. Finally, we go well beyond the traditional test role and provide direct interoperability advice and troubleshooting to warfighters in the field.

5. 5 JITC�s Areas of Expertise As we�ve executed those roles and missions, we�ve developed a broad range of subject matter experts. Many mistakenly categorize JITC as simply communications testers. It�s true that we have a great deal of capability to test and fix communications interoperability problems � and that�s important since comms provide the connectivity backbone necessary for forces to exchange information. But just scanning this list - which is not all inclusive - you can see that we have forged far beyond communications and are now engaged in the critical functions that rely on interoperability. In every one of these areas, we have a team of experts dedicated to working interoperability testing and issues. And in almost every one of these areas, we actually have dedicated test facilities either at Fort Huachuca or at Indian Head, MD.As we�ve executed those roles and missions, we�ve developed a broad range of subject matter experts. Many mistakenly categorize JITC as simply communications testers. It�s true that we have a great deal of capability to test and fix communications interoperability problems � and that�s important since comms provide the connectivity backbone necessary for forces to exchange information. But just scanning this list - which is not all inclusive - you can see that we have forged far beyond communications and are now engaged in the critical functions that rely on interoperability. In every one of these areas, we have a team of experts dedicated to working interoperability testing and issues. And in almost every one of these areas, we actually have dedicated test facilities either at Fort Huachuca or at Indian Head, MD.

6. 6 Not only do we employ our own extensive test facilities to advance interoperability, but we also collaborate with other experts and their facilities via a distributed test network. For example, approximately once a month we�ll run a joint test for systems operating over the joint data network using tactical information links (like TADIL J). We connect to service and agency systems like PATRIOT and AWACS at labs across the country (or even world), stimulate them from our central facility to make them think they�re seeing friendly and hostile tracks, and collect detailed data on the information they exchange. After the tests, JITC, JFCOM, and the services and agencies meet to evaluate how effectively the systems and forces interoperated to accomplish the mission. We do a significant portion of our testing today in a distributed fashion. But we are working hard to expand and improve the fidelity of the distributed testing. For instance, DoD tasked DISA and JITC with the Joint Distributed Engineering Plant. (click mouse) The JDEP vision is to provide the infrastructure, process, and expertise to replicate joint environments which developers, testers, and engineers can use to work through interoperability issues throughout a system�s lifecycle. Just as no single operational entity constitutes a joint task force, neither can any single engineering or test agency replicate a realistic joint environment. However, JDEP is founded on the notion that, through collaboration of existing engineering and testing facilities we can develop highly realistic joint environments to work through technical and procedural interoperability issues. The JDEP exists today and has been actively supporting the SIAP System Engineer and the Theater Air and Missile Defense communities. DoD has funded JDEP to continue to expand into multiple functional areas over the next 4 years.Not only do we employ our own extensive test facilities to advance interoperability, but we also collaborate with other experts and their facilities via a distributed test network. For example, approximately once a month we�ll run a joint test for systems operating over the joint data network using tactical information links (like TADIL J). We connect to service and agency systems like PATRIOT and AWACS at labs across the country (or even world), stimulate them from our central facility to make them think they�re seeing friendly and hostile tracks, and collect detailed data on the information they exchange. After the tests, JITC, JFCOM, and the services and agencies meet to evaluate how effectively the systems and forces interoperated to accomplish the mission. We do a significant portion of our testing today in a distributed fashion. But we are working hard to expand and improve the fidelity of the distributed testing. For instance, DoD tasked DISA and JITC with the Joint Distributed Engineering Plant. (click mouse) The JDEP vision is to provide the infrastructure, process, and expertise to replicate joint environments which developers, testers, and engineers can use to work through interoperability issues throughout a system�s lifecycle. Just as no single operational entity constitutes a joint task force, neither can any single engineering or test agency replicate a realistic joint environment. However, JDEP is founded on the notion that, through collaboration of existing engineering and testing facilities we can develop highly realistic joint environments to work through technical and procedural interoperability issues. The JDEP exists today and has been actively supporting the SIAP System Engineer and the Theater Air and Missile Defense communities. DoD has funded JDEP to continue to expand into multiple functional areas over the next 4 years.

7. 7 Demos and Exercises Distributed Interoperability Communications Exercise (DICE) Joint interoperability Voice Switches Data Systems Messaging Systems Transmission Systems Video Teleconference Operational units in doctrinally deployed joint network Comms training in a JTF environment In addition to testing in a laboratory environment, we also test in field environments. JWID (which is supported by our test division at Indian Head, MD) is the Joint Chiefs of Staff annual event that enables the US combatant commands and international community to investigate C4 solutions that focus on relevant and timely objectives for enhancing coalition interoperability Listed are the 6 primary objectives of JWID 2003. This year, there are 60 Coalition Interoperability Trials to address these objectives for both technical interoperability and warfighter utility. The host combatant commander is PACOM (will switch to NORTHCOM for 04 and 05). Other key participants include EUCOM, STRATCOM, TRANSCOM, DISA, NIMA, NSA, DIA and each of the services. Allied participation includes Canada, Australia, New Zealand, UK, Spain, and NATO. DICE (supported by a test division at Fort Huachuca, AZ) is a major joint communications exercise where Combatant Commanders, Services, and Agencies nominate systems to be tested for interoperability in a joint environment. JITC, under JFCOM sponsorship, replicates a Joint Task Force communications environment in order to mitigate operational risk by thoroughly testing new communications systems and software releases in a realistic joint tactical network. Most of the systems tested during DICE are candidates for joint certification, although less formal interoperability assessments for emerging systems are conducted as well. JITC�s approach to testing during DICE includes a combination of DOD testbeds, DISN Standardized Tactical Entry Points, and operational units from each of the armed services distributed throughout the U.S., afloat, and abroad. This year, like last, DICE is playing a key role by providing critical support to deployed and deploying units. In addition to testing in a laboratory environment, we also test in field environments. JWID (which is supported by our test division at Indian Head, MD) is the Joint Chiefs of Staff annual event that enables the US combatant commands and international community to investigate C4 solutions that focus on relevant and timely objectives for enhancing coalition interoperability Listed are the 6 primary objectives of JWID 2003. This year, there are 60 Coalition Interoperability Trials to address these objectives for both technical interoperability and warfighter utility. The host combatant commander is PACOM (will switch to NORTHCOM for 04 and 05). Other key participants include EUCOM, STRATCOM, TRANSCOM, DISA, NIMA, NSA, DIA and each of the services. Allied participation includes Canada, Australia, New Zealand, UK, Spain, and NATO. DICE (supported by a test division at Fort Huachuca, AZ) is a major joint communications exercise where Combatant Commanders, Services, and Agencies nominate systems to be tested for interoperability in a joint environment. JITC, under JFCOM sponsorship, replicates a Joint Task Force communications environment in order to mitigate operational risk by thoroughly testing new communications systems and software releases in a realistic joint tactical network. Most of the systems tested during DICE are candidates for joint certification, although less formal interoperability assessments for emerging systems are conducted as well. JITC�s approach to testing during DICE includes a combination of DOD testbeds, DISN Standardized Tactical Entry Points, and operational units from each of the armed services distributed throughout the U.S., afloat, and abroad. This year, like last, DICE is playing a key role by providing critical support to deployed and deploying units.

8. 8 Operational Support Both JWID and DICE are designed specifically for evaluating interoperability. But JITC also plays an interoperability support role in a number (6-10) of other exercises sponsored by Combatant Commanders. Here you see a sampling of these exercises. Our support is task-organized and unique to each customer�s particular needs. Subject matter experts provide interoperability assistance to the commander�s staff, component headquarters and tactical communications units throughout the planning and execution phases of each exercise. But even more important than our exercise support, JITC provides interoperability assistance directly to warfighters in contingencies. (Click Mouse). This outer ring shows the operations JITC has supported over the years. We continuously run a Hotline to respond to interoperability issues warfighters are experiencing. In addition, we have LNOs assigned to every combatant commander � 5 of which are actually collocated with the warfighter: 2 at JFCOM, and 1 each at PACOM, CENTCOM, and NATO HQ. The combination of our LNOs and Hotline accessibility help us to anticipate interoperability obstacles and respond to actual problems. Our responses range from working through the issue on the phone, to replicating the issue in our facilities, to deploying interoperability experts to theater. The most recent example is Operation ENDURING FREEDOM. We have responded to 349 hotline calls since 9-11-01, 146 of which are OEF specific. JITC first deployed a team on 9-17-01, and have had people on-site in theater and at CENTCOM headquarters until the present. In fact, an Army command we supported awarded the Bronze Star to one of our communication NCOs for his efforts in Afghanistan. JITC OEF support ranged from Tactical Data Links supporting COP to satellite communications and from network management to the Defense Red Switch Network. Our support also bridges both the technical and operational aspects of interoperability: approximately 40% of the problems we solve are equipment-based, while the other 60% are to due procedural and/or training issues.Both JWID and DICE are designed specifically for evaluating interoperability. But JITC also plays an interoperability support role in a number (6-10) of other exercises sponsored by Combatant Commanders. Here you see a sampling of these exercises. Our support is task-organized and unique to each customer�s particular needs. Subject matter experts provide interoperability assistance to the commander�s staff, component headquarters and tactical communications units throughout the planning and execution phases of each exercise. But even more important than our exercise support, JITC provides interoperability assistance directly to warfighters in contingencies. (Click Mouse). This outer ring shows the operations JITC has supported over the years. We continuously run a Hotline to respond to interoperability issues warfighters are experiencing. In addition, we have LNOs assigned to every combatant commander � 5 of which are actually collocated with the warfighter: 2 at JFCOM, and 1 each at PACOM, CENTCOM, and NATO HQ. The combination of our LNOs and Hotline accessibility help us to anticipate interoperability obstacles and respond to actual problems. Our responses range from working through the issue on the phone, to replicating the issue in our facilities, to deploying interoperability experts to theater. The most recent example is Operation ENDURING FREEDOM. We have responded to 349 hotline calls since 9-11-01, 146 of which are OEF specific. JITC first deployed a team on 9-17-01, and have had people on-site in theater and at CENTCOM headquarters until the present. In fact, an Army command we supported awarded the Bronze Star to one of our communication NCOs for his efforts in Afghanistan. JITC OEF support ranged from Tactical Data Links supporting COP to satellite communications and from network management to the Defense Red Switch Network. Our support also bridges both the technical and operational aspects of interoperability: approximately 40% of the problems we solve are equipment-based, while the other 60% are to due procedural and/or training issues.

9. 9 Conclusions The examples of command & control and intelligence that I presented at the beginning of the brief illustrate well the vital importance of interoperability. They also reaffirm that, as technology and doctrine evolve, we�ll continue to experience new interoperability problems. But while we won�t ever achieve interoperability once and for all, we will continue to make accomplishments - even transformational accomplishments - as DoD implements a top-down, COCOM-centric approach. Key to the success of this approach will be extensive partnering and resource sharing, especially among systems engineers and testing organizations. JITC is already partnering with the COCOMs, services and agencies, industry, and coalition organizations; and we�re looking to strengthen and expand such partnerships. We offer our vast distributed test infrastructure, broad functional expertise, established operational experience, and our dedication to increasing combat effectiveness through interoperability. The examples of command & control and intelligence that I presented at the beginning of the brief illustrate well the vital importance of interoperability. They also reaffirm that, as technology and doctrine evolve, we�ll continue to experience new interoperability problems. But while we won�t ever achieve interoperability once and for all, we will continue to make accomplishments - even transformational accomplishments - as DoD implements a top-down, COCOM-centric approach. Key to the success of this approach will be extensive partnering and resource sharing, especially among systems engineers and testing organizations. JITC is already partnering with the COCOMs, services and agencies, industry, and coalition organizations; and we�re looking to strengthen and expand such partnerships. We offer our vast distributed test infrastructure, broad functional expertise, established operational experience, and our dedication to increasing combat effectiveness through interoperability.

10. The perspective we take in our testing is more than just making sure one piece of equipment works with another. The broad JITC focus includes the People and Procedures, as well as the Equipment. We cannot deploy our warfighters with C4I equipment of uncertain capabilities. The JITC goal is to ensure that the battlefields of tomorrow do not become the testing ground for C4I systems. The perspective we take in our testing is more than just making sure one piece of equipment works with another. The broad JITC focus includes the People and Procedures, as well as the Equipment. We cannot deploy our warfighters with C4I equipment of uncertain capabilities. The JITC goal is to ensure that the battlefields of tomorrow do not become the testing ground for C4I systems.