Semi-annual Status of  Interoperability Testing

Semi-annual Status of Interoperability Testing PowerPoint PPT Presentation


  • 187 Views
  • Uploaded on
  • Presentation posted in: General

Purpose Facing page. The Joint Interoperability Test Command (JITC) briefs the MCEB semi-annually concerning the status of interoperability testing within DoD.Provides an assessment of a given functional area -- including which systems are participating in certification testing and how well they ar

Download Presentation

Semi-annual Status of Interoperability Testing

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


1. Semi-annual Status of Interoperability Testing Given to the MCEB on 01 FEB 2001 Robert D. Hickman Joint Interoperability Test Command (JITC) [email protected]

2. Purpose Facing page The Joint Interoperability Test Command (JITC) briefs the MCEB semi-annually concerning the status of interoperability testing within DoD. Provides an assessment of a given functional area -- including which systems are participating in certification testing and how well they are faring. Way to vet problem issues the JITC and Interoperability Policy and Test Panel (IPTP) that need MCEB assistance. Unlike the normal briefing, JITC is providing information to the MCEB on JITC’s newly initiated Combined Interoperability Test (CIT) Program. This test program is not the end-all solution to combined interoperability. US policy decisions largely dictate the extent of interoperability we’ll have with other countries. Our allied and coalition partners have specific COMSEC agreements with the US, and each of these affect our ability to achieve true secure interoperability.

3. Purpose JITC responsible for providing periodic updates concerning the status of interoperability testing. This brief informs the MCEB on the initiation of the Combined Interoperability Test (CIT) Program. The Joint Interoperability Test Command (JITC) briefs the MCEB semi-annually concerning the status of interoperability testing within DoD. Typically, the briefing provides an assessment of a given functional area -- including the extent to which systems are participating in the certification process and how well participating systems are faring under test. In addition to providing this information, the briefing usually includes problematic issues for which the JITC and the Interoperability Policy and Test Panel (IPTP) are requesting the MCEB’s assistance. This briefing diverges from the system- and issues-based approach and simply provides information to the MCEB on JITC’s newly initiated Combined Interoperability Test (CIT) Program. The Joint Interoperability Test Command (JITC) briefs the MCEB semi-annually concerning the status of interoperability testing within DoD. Typically, the briefing provides an assessment of a given functional area -- including the extent to which systems are participating in the certification process and how well participating systems are faring under test. In addition to providing this information, the briefing usually includes problematic issues for which the JITC and the Interoperability Policy and Test Panel (IPTP) are requesting the MCEB’s assistance. This briefing diverges from the system- and issues-based approach and simply provides information to the MCEB on JITC’s newly initiated Combined Interoperability Test (CIT) Program.

4. CIT Program – Background Facing Page Combined interoperability has long been an issue with the CINCs, but no funding was programmed to support a CIT program. Combined interoperability testing has occurred. At times, customers have provided their own funding. For example, since 1996 EUCOM has provided Partners for Peace funding to JITC to support their annual COMBINED ENDEAVOR exercise. Additionally, if a CINC prioritized a combined interoperability issue, JITC would fund it from our CINC-support budget. Examples of this are the TADIL testing conducted with Australia and other nations within the PACOM AOR at the CINC’s request. DISA submitted a special budget issue in support of combined interoperability testing in 1999. A PDM approved the funding starting in FY01. This funding is vital to helping identify and solve combined interoperability issues, and will support the CINCs’ priority testing requirements.

5. CIT Program - Background -While combined interoperability has long been an issue with the CINCs, there historically was no funding programmed to directly support combined interoperability testing. -That is not to say that no combined interoperability testing took place. At times, customers have provided their own funding. For example, since 1996 EUCOM has provided Partners for Peace funding to JITC to support their annual COMBINED ENDEAVOR exercise. Additionally, if a CINC prioritized a combined interoperability issue, JITC would fund it from our CINC-support budget. Examples of this are the TADIL testing conducted with Australia and other nations within the PACOM AOR at the CINC’s request. -But in order to provide dedicated funding for a programmatic approach to combined interoperability, DISA submitted a special budget issue in 1999. A program decision memorandum approved the funding starting in FY01. -This funding is vital to helping identify and solve combined interoperability issues, and as you will see throughout the remainder of the brief, the funding will support the CINCs’ priority testing requirements. But this test program is not the end-all solution to combined interoperability. US policy largely dictates the extent of interoperability we’ll have with other countries. For example, allied and coalition countries have specific COMSEC agreements with the US, and each of these affect our ability to achieve true secure interoperability. You also heard about these issues during the J6T briefings on Coalition Interoperability and CCEB CWAN -While combined interoperability has long been an issue with the CINCs, there historically was no funding programmed to directly support combined interoperability testing. -That is not to say that no combined interoperability testing took place. At times, customers have provided their own funding. For example, since 1996 EUCOM has provided Partners for Peace funding to JITC to support their annual COMBINED ENDEAVOR exercise. Additionally, if a CINC prioritized a combined interoperability issue, JITC would fund it from our CINC-support budget. Examples of this are the TADIL testing conducted with Australia and other nations within the PACOM AOR at the CINC’s request. -But in order to provide dedicated funding for a programmatic approach to combined interoperability, DISA submitted a special budget issue in 1999. A program decision memorandum approved the funding starting in FY01. -This funding is vital to helping identify and solve combined interoperability issues, and as you will see throughout the remainder of the brief, the funding will support the CINCs’ priority testing requirements. But this test program is not the end-all solution to combined interoperability. US policy largely dictates the extent of interoperability we’ll have with other countries. For example, allied and coalition countries have specific COMSEC agreements with the US, and each of these affect our ability to achieve true secure interoperability. You also heard about these issues during the J6T briefings on Coalition Interoperability and CCEB CWAN

6. CIT Funding and Requirements Facing page First year that combined interoperability has had a dedicated funding line. We are scheduled to receive $3M, $3.8M, $4M and $4M in FY 02-05, respectively. Lessons learned from this process: CINCs perceive that they were being asked for same information from multiple organizations The Joint Battle Center (JBC), the CINC Interoperability Program Offices (CIPOs), JWICs and JITC. In the future, JITC will work the identification and prioritization of requirements through the Joint Staff in coordination with JFCOM. This will consolidate the requirements identification process and insure that issues are assigned to the appropriate organization for action and coordination.

7. CIT Funding and Requirements JITC received $3M for FY01 - the first year that combined interoperability has had a dedicated funding line. We are scheduled to receive $3M, $3.8M, $4M and $4M in FY 02-05, respectively. This slide outlines the general process that we followed to allocate the funding to specific tasks in support of the CINCs. Four CINCs responded to our request to identify combined interoperability test requirements: CENTCOM, PACOM, EUCOM, and JFCOM. The next few slides show examples of the support requested by and to be provided to the geographical CINCs. JITC will also provide support to JFCOM, but since that support ultimately is directed towards the geographic CINCs, we have not listed them separately. Note that one of the lessons learned from following this process was that CINCs felt that they were being asked for interoperability issues from several sources. For this reason and due to the fact that we believe that the CIT requirements will expand in the coming years, JITC will work the identification and prioritization of requirements through the Joint Staff in coordination with JFCOM. This will consolidate the requirements identification process and insure that issues are assigned to the appropriate organization for action and coordination. JITC received $3M for FY01 - the first year that combined interoperability has had a dedicated funding line. We are scheduled to receive $3M, $3.8M, $4M and $4M in FY 02-05, respectively. This slide outlines the general process that we followed to allocate the funding to specific tasks in support of the CINCs. Four CINCs responded to our request to identify combined interoperability test requirements: CENTCOM, PACOM, EUCOM, and JFCOM. The next few slides show examples of the support requested by and to be provided to the geographical CINCs. JITC will also provide support to JFCOM, but since that support ultimately is directed towards the geographic CINCs, we have not listed them separately. Note that one of the lessons learned from following this process was that CINCs felt that they were being asked for interoperability issues from several sources. For this reason and due to the fact that we believe that the CIT requirements will expand in the coming years, JITC will work the identification and prioritization of requirements through the Joint Staff in coordination with JFCOM. This will consolidate the requirements identification process and insure that issues are assigned to the appropriate organization for action and coordination.

8. FY01 CIT Requirements Facing page On-site Reps Provide real-time identification and coordination of the combined issues at each CINC: Combined Interoperability Handbooks Document existing architecture as demonstrated during exercises TADIL Testing Evaluate combined interoperability CCIBs Provide Testing support to PACOM and CENTCOM formal combined interoperability panels Representative specific system test requirements CNR: Evaluate and report on interoperability between US Marine and Australian Defence Force radios ROVING SANDS: Interoperability evaluation and technical support ADSI: Joint/Combined Interoperability Certification

9. FY01 CIT Requirements On-site Reps help provide real-time identification and coordination of the combined issues at each CINC: CENTCOM: In place Jan 01, PACOM: In place Jan 01, EUCOM: Processing through the German government Technical Expert Status Agreement (TESA process). This process is necessary to determine that a German national could not fill the position and the position will, in fact, require a US citizen. We expect this process to be completed Feb/Mar 01, JFCOM: In place Jan 01, NATO: In place Jan 01 Combined Interoperability Handbook: CENTCOM, PACOM, EUCOM TADIL Testing: CENTCOM, PACOM, JFCOM, NATO CCIB: CENTCOM, PACOM Combat Net Radios: PACOM ROVING SANDS: JFCOM ADSI: CENTCOM, JFCOMOn-site Reps help provide real-time identification and coordination of the combined issues at each CINC: CENTCOM: In place Jan 01, PACOM: In place Jan 01, EUCOM: Processing through the German government Technical Expert Status Agreement (TESA process). This process is necessary to determine that a German national could not fill the position and the position will, in fact, require a US citizen. We expect this process to be completed Feb/Mar 01, JFCOM: In place Jan 01, NATO: In place Jan 01 Combined Interoperability Handbook: CENTCOM, PACOM, EUCOM TADIL Testing: CENTCOM, PACOM, JFCOM, NATO CCIB: CENTCOM, PACOM Combat Net Radios: PACOM ROVING SANDS: JFCOM ADSI: CENTCOM, JFCOM

10. FY01 CIT Requirements (cont) Facing Page Representative specific system test requirements (cont) STE: Evaluate combined interoperability DMS: Evaluate combined interoperability CATHODE EMISSION: Technical support, document equipment configurations and interoperability evaluation NATO Committees NIETWG establishes NATO testing policy/procedures, validates testing requirements and archives testing results ISTWG identifies tools to assist the warfighter/planner NIETI implements the testing program for NATO

11. FY01 CIT Requirements (cont) TACTICAL STE: EUCOM (STE = Secure Terminal Equipment) DMS: EUCOM (DMS = Defense Message System) CATHODE EMISSION : EUCOM (Northern Region Communications and Information Systems Interoperability Exercise) Other Requirements (BACKUP) CENTCOM: Shared Early Warning (SEW) and Airborne Integrated Terminal Group (AITG) PACOM: Parakeet Circuit Switch, CWAN and TEAM CHALLENGE JFCOM: Multi-level Security and Secure Voice, Collaborative Planning Tools NATO: Czech Republic Tactical Switch and NATO Secondary Imager Format (NSIF)TACTICAL STE: EUCOM (STE = Secure Terminal Equipment) DMS: EUCOM (DMS = Defense Message System) CATHODE EMISSION : EUCOM (Northern Region Communications and Information Systems Interoperability Exercise) Other Requirements (BACKUP) CENTCOM: Shared Early Warning (SEW) and Airborne Integrated Terminal Group (AITG) PACOM: Parakeet Circuit Switch, CWAN and TEAM CHALLENGE JFCOM: Multi-level Security and Secure Voice, Collaborative Planning Tools NATO: Czech Republic Tactical Switch and NATO Secondary Imager Format (NSIF)

12. Conclusions and Recommendations Facing page FY01 is the first year funding has been dedicated to support combined interoperability testing. JITC’s CIT program will systematically address the CINCs’ priority combined testing issues. Results of the tests will be maximized by integrating them into the full scope of combined interoperability issues, to include operational requirements and engineering solutions. The synchronization process currently being implemented for joint interoperability will also meet combined interoperability requirements. Request MCEB endorsement of our program and way ahead.

13. Recommendations FY01 marks the first year funding has been dedicated to support combined interoperability testing. JITC has developed a CIT program to insure we systematically address the CINCs’ priority combined testing issues. The results and impacts of the testing program will be maximized by integrating it into the larger combined interoperability picture to include operational requirements and engineering solutions. JS and JFCOM synchronization of the organizations responsible for these various aspects will help insure proper follow-through on actions such as scheduling interoperability testing for proposed engineering solutions or proposing engineering solutions to shortfalls identified during testing. We seek your endorsement for continuing the Combined Interoperability Program. This synchronization process is currently being implemented for joint interoperability, and the combined interoperability process need not differ significantly. JITC will conduct the initial efforts in coordination with JFCOM and raise issue we are unable to resolve to DISA/IPTP/MCEB as required. We ask that you endorse this process. FY01 marks the first year funding has been dedicated to support combined interoperability testing. JITC has developed a CIT program to insure we systematically address the CINCs’ priority combined testing issues. The results and impacts of the testing program will be maximized by integrating it into the larger combined interoperability picture to include operational requirements and engineering solutions. JS and JFCOM synchronization of the organizations responsible for these various aspects will help insure proper follow-through on actions such as scheduling interoperability testing for proposed engineering solutions or proposing engineering solutions to shortfalls identified during testing. We seek your endorsement for continuing the Combined Interoperability Program. This synchronization process is currently being implemented for joint interoperability, and the combined interoperability process need not differ significantly. JITC will conduct the initial efforts in coordination with JFCOM and raise issue we are unable to resolve to DISA/IPTP/MCEB as required. We ask that you endorse this process.

  • Login