Bidders Library Interoperability Test and Evaluation - JITP 3006.pdf

FOR OFFICIAL USE ONLY

DEFENSE INFORMATION SYSTEMS AGENCY

JOINT INTEROPERABILITY TEST COMMAND

FORT HUACHUCA, ARIZONA

JOINT INTEROPERABILITY

TEST PLAN 3006

FOR TESTING

TACTICAL DATA LINKS

February 2019 This plan supersedes JITC Plan 3006 dated May 2015 and JITC Plan 3014 dated April 2007

DISTRIBUTION: Distribution authorized to DoD and DoD Contractors only; for Official Use only. Other requests for this document shall be referred to the DISA’s Foreign Disclosure Office and JITC’s Data Links Branch, Joint Interoperability Test Command.

This document has been determined to be releasable to the Australia, Japan, New Zealand, Republic of Korea, Singapore, and Thailand.

JOINT INTEROPERABILITY

TEST PLAN 3006

FOR TESTING

TACTICAL DATA LINKS

NOVEMBER 2018

Submitted by: Robin S. Murray Chief, Data Links Branch

Approved by: _____________________________

TOD WISTER

Chief, Tactical Systems Division

Prepared Under the Direction of:

Steven V. Hooper Joint Interoperability Test Command

Fort Huachuca, Arizona

(This page intentionally left blank.)

EXECUTIVE SUMMARY

Department of Defense (DoD) Instruction 8330.01 establishes the Defense Information Systems Agency, Joint Interoperability Test Command (JITC), as the sole DoD certification authority for joint and standards conformance certification. Chairman of the Joint Chiefs of Staff Instruction 6610.01 and the JITC Interoperability Process Guide provide additional instructions regarding testing of Tactical Data Links (TDLs) for interoperability. To accomplish this mission for systems that implement TDLs, JITC conducts, witnesses, or verifies interoperability and standards conformance testing during the development, acquisition, and maintenance of Information Technology (IT) and National Security Systems (NSS).

This Joint Interoperability Test Plan establishes the concept and methodology for testing IT/NSS implementing TDLs. It addresses the approach and processes for TDL test planning, design, execution, analysis, and reporting.

JITC TDL testing addresses joint interoperability, combined interoperability, and standards conformance. Joint interoperability testing assesses whether tactical data systems can properly process and interpret prescribed data while participating in a joint TDL network. Combined interoperability testing assesses whether coalition tactical data systems can properly process and interpret prescribed data while participating in a United States coalition-combined TDL network. Standards conformance testing verifies that required transactions, messages, data fields, data items, and all values conform to the structure and content of the appropriate military standard.

The DoD requires that systems successfully complete testing in an operationally realistic environment prior to receiving a system interoperability certification.

ii iii

TABLE OF CONTENTS

Page

EXECUTIVE SUMMARY .............................................................................................. i

JOINT INTEROPERABILITY TEST BACKGROUND

TACTICAL DATA LINK TESTING DESCRIPTION

TYPES OF TESTING

SCOPE

PURPOSE

APPLICABILITY

LIMITATIONS

TACTICAL DATA LINK TEST ENTRANCE CRITERIA

TEST SCHEDULING

RESULTS

APPENDICES

ACRONYMS ............................................................................................................. A1 JOINT INTEROPERABILITY TEST METHODOLOGY ............................................. B1 TROUBLE REPORT ASSESSMENT DEFINITIONS ................................................ C1 PLAN OF ACTION AND MILESTONES ................................................................... D1

TACTICAL DATA LINK PRELIMINARY TROUBLE REPORT INSTRUCTIONS ...... E1

JOINT ANALYSIS REVIEW PANEL/ANALYSIS REVIEW PANEL PROCESS ........ F1

JOINT INTEROPERABILITY TEST CONDUCT PROTOCOL .................................. G1 COMBINED INTEROPERABILITY TEST METHODOLOGY .................................... H1 INTEGRATED BROADCAST SERVICE ..................................................................... I1

VARIABLE MESSAGE FORMAT STANDARDS CONFORMANCE .......................... J1

TACTICAL DATA LINK TEST NETWORK CONFIGURATION ................................. K1 STANDARDS CONFORMANCE METHODOLOGY .................................................. L1

UNITED STATES MESSAGE TEXT FORMAT STANDARDS CONFORMANCE .... M1

AUTOMATED TEST CASE GENERATOR ............................................................... N1 REFERENCES ......................................................................................................... O1 iv

LIST OF FIGURES

Figure E-1 Tactical Data Link Preliminary Trouble Report Form .............................. E2 Figure I-1 IBS Communications Architecture ........................................................... I3 Figure I-2 IBS-NS System Data Flow ....................................................................... I4 Figure I-3 IBS Enterprise Operational Architecture .................................................... I5 Figure I-4 Certification Path ....................................................................................... I8 Figure I-5 Certification Test Building Block Approach ................................................ I9 Figure I-6 SCT Applicability Process ........................................................................ I11 Figure I-7 Normal Distribution – Standard Deviation Graph ..................................... I27 Figure I-8 MFL Test Infrastructure ........................................................................... I33 Figure I-9 MFL IBS OTA Test Architecture and Data Flow ...................................... I36 Figure I-10 MFL Network Test Architecture and Data Flow ..................................... I37 Figure J-1 Typical VMF SCT Configuration .............................................................. J7 Figure K-1 Notional Joint Interoperability Network Architecture ............................... K2 Figure K-2 JIT Notional TDL Configuration Diagram ................................................ K3 Figure L-1 Normal Distribution – Standard Deviation Graph ..................................... L3 Figure M-1 Typical USMTF SCT Network Configuration .......................................... M6

LIST OF TABLES

Table 1 TDL Test Entrance Criteria Table 2 Service-Level Documentation Requirements Table 3 Example JIT Test Schedule Table B-1 TDL Test Cycle ........................................................................................ B2 Table C-1. Interoperability Trouble Report Categories ............................................. C1 Table C-2. Mission Status ........................................................................................ C2 Table C-3. Standards Conformance Trouble Report Categories ............................. C2 Table C-4. Combined Interoperability Test Trouble Report Categories ................... C2 Table C-5. Trouble Report Prefix Definitions ........................................................... C3 Table C-6. Trouble Report Class Descriptions ......................................................... C3 Table E-1. Preliminary Trouble Report Fields and Field Descriptions ...................... E2 Table E-2. Service/Agency Preliminary Trouble Report Number Blocks .................. E4 Table I-1. IBS CMF Implementation Applicability ..................................................... I12 Table I-2. IBS CMF-to-Link 16 Message Subtype Translations ............................... I14 Table I-3. Link 16-to-IBS CMF Message Subtype Translations ............................... I15 Table I-4. IBS Data Correctness Criteria .................................................................. I18 Table I-5. IBS Timeliness Criteria ............................................................................ I19 Table I-6. CMF Standards Conformance Collection Requirements (Excerpt) .......... I21 Table I-7. CMF-to-Link 16 Translation Standards Conformance Collection

Requirements (Excerpt) ....................................................................................... I23 v

LIST OF TABLES (Continued)

Table I-8. Link 16-to-CMF Translation Standards Conformance Collection Requirements (Excerpt) ....................................................................................... I25

Table I-9. Degrees of Risk Definitions ...................................................................... I28 Table I-10. Interoperability Sampling Collection Requirements ............................... I30 Table I-11. Interoperability Trouble Report Categories ............................................ I31 Table I-12. Example SUT CMF DFI/DUI Data Element Sample Results ................. I38 Table I-13. Example SUT CMF Message Subtype Data Element Results ......... IError!

Bookmark not defined.

Table I-14. Example SUT CMF-Legacy Message Format Translation Conformance

Results ................................................................................................................ I40 Table I-15. Example SUT CMF-to-Link 16 Translation DFI/DUI Data Element Results ................................................................................................................... I41 Table I-16. Example SUT CMF-to-Link 16 Message Subtype Transaction Translation

Results .................................................................. IError! Bookmark not defined.

Table I-17. Example SUT Link 16-to-CMF Translation DFI/DUI Data Element Results ................................................................................................................... I43 Table I-18. Example SUT Link 16-to-CMF Message Subtype Transaction Translation

Results .................................................................. IError! Bookmark not defined.

Table I-19. Example SUT NR KPP Compliance Status ........................................... I45 Table I-20. Example SUT Joint Critical Task Results for Mission 1 ......................... I45 Table I-21. NR KPP Attribute Status ........................................................................ I46 Table I-22. Overall NR KPP Status .......................................................................... I46 Table I-23. Standards Conformance Deficiency Report Categories ......................... I46 Table I-24. Example DRs Assigned to SUT ............................................................. I47 Table I-25. Example Key Technical Deficiencies ..................................................... I48 Table J-1. Previous VMF Standards ......................................................................... J1 Table J-2. VMF Messages That Display Warfighter Symbology ............................... J2 Table J-3. Levels of MIN IMP Requirements ............................................................ J3 Table J-4. VMF Standard Message Level MIN IMP .................................................. J4 Table J-5. Example VMF Messages to Input/Output Threads .................................. J6 Table J-6. VMF-Certified Test Tools ......................................................................... J8 Table J-7. VTT Database Information ....................................................................... J9 Table J-8. VMF Test Message Naming Convention ................................................ J12 Table J-9. Example MIL-STD-6017 Data Definition ................................................ J12 Table L-1. Degree of Risk Definition ......................................................................... L3 Table L-2. Sample Results for J3.2 Data Element Transmit Requirements .............. L4 Table L-3. Sample Results for the Air Surveillance Functional Area ......................... L5 Table L-4. Sample Results for System Status (Notional) .......................................... L6 Table L-5. Sample TR Summary............................................................................... L6 Table L-6. Sample Conformance Risk ...................................................................... L7 Table L-7. Standards Conformance Trouble Report Categories ............................... L7 Table M-1. Previous USMTF Standards .................................................................. M2 vi

Table M-2. USMTF Messages That Display Warfighter Symbology ........................ M3 LIST OF TABLES (Continued)

Table M-3. USMTF Common Information Exchange ............................................... M3 Table M-3. USMTF Common Information Exchange (continued) ............................ M4 Table M-4. Example USMTF Messages to Input/Output Threads ........................... M5 Table M-5. USMTF Test Message Naming Convention ......................................... M10 Table M-6. Example MIL-STD-6040 Data Definition .............................................. M10

LIST OF EMBEDDED DOCUMENTS

TR Checklist ............................................................................................................. C3 POAM Example ........................................................................................................ D1 TDL Request Form ................................................................................................... K8 RFI Master ................................................................................................................ K8

JOINT INTEROPERABILITY TEST BACKGROUND

The Joint Interoperability Test Command (JITC) Data Links Branch (JTC4) tests Information Technology (IT)/National Security Systems (NSS) for Tactical Data Link (TDL) interoperability and standards conformance through a variety of test venues. The TDL test results are provided to Service Participating Test Unit Coordinators (PTUCs), system program offices, and JITC system certification Action Officers to support joint interoperability certification. The JITC conducts Joint Interoperability Tests (JITs) of United States (U.S.) TDL systems, Combined Interoperability Tests (CITs) of foreign systems in support of the Theater Combatant Commands (CCMDs), and Standards Conformance Tests (SCTs) of U.S. and foreign systems at the request of system program offices.

TACTICAL DATA LINK TESTING DESCRIPTION

Link 11. Link 11 is a half-duplex, netted link that normally operates by roll call from a Data Net Control Station (DNCS). Link 11 can also operate in the broadcast mode.

The roll call mode of operation used in the Link 11 interface requires that each Participating Unit (PU) respond in turn while all other stations are receiving. A DNCS initiates the roll call by addressing and transmitting an interrogation message to a specific PU that then responds by transmitting its data. The DNCS then interrogates the next PU in the prescribed roll call. Link 11 can be transmitted on High Frequency (HF) and/or Ultra High Frequency (UHF) bands. Data speed can be selected from bit rates of 2250 or 1364 bits per second (bps). Dual sideband diversity operation and Doppler shift correction features improve reliability and accuracy of data exchange. Some Data Terminal Sets (DTS) provide the option to select either the Conventional Link 11 Waveform (CLEW) or the Single tone Link 11 Waveform (SLEW). The SLEW and CLEW are not compatible waveforms. SLEW, among other enhancements, provides increased propagation and a more powerful Error Detection and Correction algorithm.

While the option exists to operate in either CLEW or SLEW, all participants in a given Link 11 network must select the same waveform to achieve connectivity between units.

Link 11 is scheduled for sunset in 2025, and Link 22 is projected to replace Link 11.

Link 11 is defined in Military Standard (MIL-STD)-6011, “Tactical Data Link (TDL) A/B Message Standard.”

Link 16. Link 16 is a node-less, high-capacity, multifunctional, secure, jam-resistant TDL designed for the exchange of fixed format and voice messages using the Joint Tactical Information Distribution System (JTIDS) Class 2, Multifunctional Information Distribution System (MIDS), MIDS Joint Tactical Radio System (JTRS) terminal or the Small Form Factor Terminals (Small Tactical Terminal, Tactical Network Corporation Tactical Radio, and Battlefield Awareness and Targeting System-Dismounted). Link 16 uses the principle of Time Division Multiple Access, an architecture that employs time slot interleaving to provide multiple, simultaneous communications networks. Since Link 16 is a UHF system, transmitted messages can only be received by units that are within Line of Sight (LOS). However, Link 16 provides a means to relay beyond LOS.

All JTIDS Units (JUs) have preassigned sets of multiple time slots to transmit their data and to receive data from other units. The time slots of a network can be parceled out to one or more Network Participation Groups (NPGs). An NPG is defined by its function and also by the types of messages that will be transmitted on it. Dividing the network into functional groups allows JUs to participate only on the NPGs for the functions they perform. Link 16 is defined in MIL-STD-6016, “Tactical Data Link J Message Standard.”

(Link 11 and Link 16 testing are addressed throughout the main body of this document.

The JIT methodology is addressed in Appendix B, and SCT testing is addressed in Appendix L.)

Variable Message Format. The Variable Message Format (VMF) is a bit-oriented digital information standard consisting of variable length messages. As digital data, VMF messages are not human-readable but are designed as a common means of exchanging digital data between combat units at various organizational levels, with varying needs for volume and detail of information. The VMF messages are applicable to a broad range of tactical communication systems. The VMF can be operated in a secure or non-secure mode and provides the user with the flexibility to send only required information, on demand, to accommodate bandwidth-constrained environments. The VMF is media-independent and can operate over any digital point-to-point or broadcast-capable radio system, since network functions are independent of the textual portion of the VMF message. The VMF is defined in MIL-STD-6017, “Interface Standard for Variable Message Format.” (The VMF testing methodology is defined in Appendix J.)

Joint Range Extension Application Protocol. The Joint Range Extension Application Protocol (JREAP) is a generalized application protocol. The JREAP enables tactical data to be transmitted over digital media and networks not designed originally for tactical data exchange. Formatted tactical digital messages are embedded in JREAP messages as data fields within available commercial and Government protocols (e.g., those used over satellites and terrestrial links). The JREAP also provides specialized management messages that transport data not contained in the formatted messages.

These management messages support TDL-unique functions. The JREAP offers users the following capabilities:

• Extends the range-limited tactical networks to beyond LOS while reducing their dependence upon relay platforms.

• Reduces the load on stressed networks.

• Provides backup communications upon the loss of the radio frequency link.

• Provides a TDL connection to a platform that may not be equipped with the specialized communications equipment for that TDL.

The JREAP is defined in MIL-STD-3011, Department of Defense, “Interface

Standard for the Joint Range Extension Application Protocol.”

Integrated Broadcast Service. The Integrated Broadcast Service (IBS) is a theater-tailored joint information environment dissemination architecture with global connectivity, employing a data-centric standardized format. It is designed to be fully interoperable with current and future tactical and strategic systems. The IBS architecture focuses on tactical information requirements and on the requirements of strategic decision makers. At full operational capability, users expect the global IBS network servers and the theater interface nodes to communicate via federated terrestrial and over-the-air networks using the Common Message Format (CMF), the format provided by all producers and processed by the Warfighters' Tactical Data Processors (TDPs). The IBS CMF is defined in MIL-STD-6018, “Integrated Broadcast Service (IBS) Common Message Format (CMF).” (The IBS testing methodology is defined in Appendix I.)

United States Message Text Format. The United States Message Text Format (USMTF) Program is a set of character-oriented message text formats used in support of Command and Control (C2) systems for the exchange of information. The objectives of the USMTF Program are to:

• Produce messages that are both machine-processable and human-readable.

• Reduce the time and effort required drafting, transmitting, analyzing, interpreting, and processing messages.

• Improve Information Exchange (IE) through vocabulary control.

• Provide uniform reporting procedures to be used in all defense conditions from peacetime through crises, war, and post-attack.

• Facilitate exchange of information between the United States and allied commands and reduce or eliminate dual reporting by U.S. units when they operate with allied commands or units or after their change of operational control to allied nations or organizations.

USMTF is defined in MIL-STD-6040, “U.S. Message Text Formatting Program.”

(USMTF testing methodology is defined in Appendix M.)

TYPES OF TESTING

The JTC4 conducts JIT, CIT, and SCT testing of all Information Technology (IT), including NSS, which implements TDLs and USMTF. The Department of Defense Instruction (DoDI) 8330.01, “Interoperability of Information Technology (IT), Including National Security Systems (NSS),” directs JITC to:

• Evaluate and certify joint, multinational, and interagency IT interoperability for the Department of Defense (DoD).

• Serve as the Interoperability Certification Authority for all DoD IT with joint, multinational, or interagency interoperability requirements.

• Establish—in coordination with the DoD Chief Information Officer, Under Secretary of Defense for Acquisition Technology and Logistics, Director of Operational Test and Evaluation, Deputy Chief Management Officer, and other DoD component heads—procedures to verify, assess, and certify through testing, joint, multinational, and interagency IT interoperability throughout a system’s life cycle.

• Coordinate with the DoD components to resolve joint, multinational, or interagency IT interoperability issues. If resolution cannot be achieved, provide an impact statement and recommendations for resolution to the Interoperability Steering Group.

• Participate in the Joint Capabilities Integration and Development System (JCIDS) review to verify that the Net Ready Key Performance Parameter (NR KPP) is adequately defined to support interoperability testing.

Tactical Data Link Joint Interoperability Test. The TDL JIT objective is to evaluate a capability, system, or service’s ability to meet the threshold and objective levels of each TDL NR-KPP element when testing a system for joint interoperability certification. The threshold level requires that the capability, system, or service must fully support execution of joint critical operational activities and IEs. The objective level requires that the capability, system, or service must fully support execution of all operational activities and IEs. For interoperability/certification testing, the system/platform shall be tested against:

• The current mandated baseline MIL-STD

• Any additional Interim Change Proposal (ICP), either Configuration Control Board

Directive (CCBD)-approved and awaiting incorporation into the MIL-STD or a U.S.-approved ICP implemented “at risk,” when the ICPs are identified to JITC by the system Service components as part of the system/platform implementation

A system should not be assigned a Preliminary Trouble Report (PTR)/Trouble

Report (TR) for not implementing a CCBD approved ICP between MIL-STD revisions (e.g., between MIL-STD-6016F and MIL-STD-6016G) unless the system/platform has voluntarily implemented the ICP. (Joint interoperability methodology is defined in Appendix B.)

Combined Interoperability Test. The TDL CIT program evaluates coalition systems that implement TDL and USMTF for Combined Interoperability. CCMDs nominate coalition TDL systems for CIT during Command and Control Interoperability Board (CCIB) meetings. The requirements for the CIT are derived from U.S. and coalition operational plans and exercises. The objective of the CIT is to determine capabilities and limitations that will enable effective communications when U.S. and coalition systems are operating together. (The CIT methodology is defined in Appendix H).

North Atlantic Treaty Organization Tactical Data Link Interoperability Testing. The JITC provides the North Atlantic Treaty Organization (NATO) with TDL interoperability assessments testing for participating NATO members and approved partner nations of the TDL Capability Team (CaT) Interoperability Testing Syndicate (ITS) (TDL CaT ITS).

The JITC TDL assessment testing enhances combined interoperability and reduces the risk to U.S. Forces operating in coalition environments.

The JITC tests to determine the extent NATO systems/software effectively implement NATO Standardization Agreements 5511, 5516, and 5616 requirements to support combined interoperability.

For detailed TDL CaT ITS procedures and processes, see the TDL CaT ITS Working Paper 48 at https://www.tacticaldatalink.net/index.php?cid=1. Request access through the site.

Standards Conformance Test. The SCT is conducted on IT/NSS that implement TDL and USMTF. SCT is a building block for interoperability and must evaluate 100 percent of the mandatory and optional requirements of the MIL-STD that are implemented by the system. The SCT is a prerequisite requirement for all JIT and CIT.

For standards conformance, a system/platform shall be tested against the current promulgated version of a MIL-STD (e.g., MIL-STD-6016), as mandated for use in the DoD Information Technology Standards Registry. For interoperability/certification testing, the system/platform shall be tested against:

• The current mandated baseline MIL-STD

• Any additional Interim Change Proposal (ICP), either Configuration Control Board

Directive (CCBD)-approved and awaiting incorporation into the MIL-STD or a U.S.-approved ICP implemented “at risk,” when the ICPs are identified to JITC by the system Service components as part of the system/platform implementation

A system should not be assigned a Preliminary Trouble Report (PTR)/Trouble

Report (TR) for not implementing a CCBD approved ICP between MIL-STD revisions (e.g., between MIL-STD-6016F and MIL-STD-6016G) unless the system/platform has voluntarily implemented the ICP. (Joint interoperability methodology is defined in Appendix B.)

The JITC has developed an automated SCT capability that is a persistent service on the test network. More information on ATC-Gen is contained in Appendix N.

SCOPE

This Joint Interoperability Test Plan (JITP) establishes the concept and methodology for testing IT/NSS implementing TDLs. It addresses the approach and processes for TDL test planning, design, execution, analysis and reporting. The JITC testing addresses both interoperability and standards conformance. Joint/combined interoperability testing assesses whether or not tactical data systems can properly process and interpret prescribed data while participating in a joint or combined tactical data network. The SCT verifies that required messages, data fields, data items and all values conform to the structure and content of the appropriate MIL-STD.

https://www.tacticaldatalink.net/index.php?cid=1

PURPOSE

This JITP:

• Establishes the concept and methodology for TDL JIT, which encompasses testing of Link 11, Link 16, IBS, JREAP, and VMF. USMTF is not part of TDLs but is tested as required.

• Establishes the concept and methodology for TDL CIT, which encompasses the combined testing (United States to coalition) of Link 11, Link 16, JREAP, and VMF. USMTF is not part of TDLs but is tested as required.

• Establishes the concept and methodology for TDL SCT, which encompasses the SCT of Link 11, Link 16, JREAP, IBS, and VMF. USMTF is not part of TDLs but is tested as required.

APPLICABILITY

This JITP applies to systems in the JIT process sponsored by the following DoD Commands and Services/Agencies (S/As):

• U.S. Army

• U.S. Navy

• U.S. Marine Corps

• U.S. Air Force

• CCMDs

• DoD agencies

• JITC

• Other DoD components as designated

LIMITATIONS

The TDL JIT is conducted in a controlled laboratory environment. Because of this, the operational realism of sensor input, operator interaction, sensor registration effects, and environmental propagation are not available. In addition, emulators such as simulators, sensor stimulations, communication loads and scenario densities, and tactical communications equipment are used vice TDL system terminals; therefore, most of the network management and host/terminal requirements are not be evaluated during a TDL JIT.

Sensor Stimulation. The test network supports sensor stimulation for only some of the test participants; therefore, JITC will use a Link 16 simulator to test systems for MIL- STD compliance with requirements predicated by a common tactical picture, including automatic track correlation. Correlation is the analysis of track reports to select those tracks representing the same object, a process that C2 Interface Units (IUs) normally accomplish automatically, but which the operator may also accomplish manually.

Problems in this area can intensify the number of dual designations where two IUs report the same object using two different track numbers. The Link 16 simulator replicates the environment necessary to adequately test the correlation capabilities of the SUTs; therefore, this limitation poses a low level of risk to the Warfighter.

Communications Loads and Scenario Densities. The TDL JIT will not include communications loads and scenario densities that may occur in a stressed tactical environment. The JITC uses operationally realistic multi-TDL test configurations;

however, test scenarios will use loads of less than 12 tracks per event to support real-time message analysis. This testing, when combined with Service-level testing, provides reasonable assurance that the SUTs will operate effectively in a stressed tactical environment; therefore, this limitation poses a low level of risk to the Warfighter.

Tactical Communications Equipment. Participating systems will be able to transmit and receive Link 11, Link 16, JREAP, and VMF messages over Internet Protocol (IP)-based standard communications circuits without the use of tactical radios or JTIDS/MIDS terminals. The TDL JIT will not be able to test the Link 16 Network Manager functional area because the test configuration does not include JTIDS/MIDS terminals. The JITC cannot test JREAP Appendix A or JREAP Appendix B in a terrestrial environment due to the serial nature of those protocols. The JITC does not yet have the capability to test Link 22. Services test these capabilities during Service-level testing, and users constantly evaluate these media capabilities in the field and during live exercises; therefore, this limitation poses a low level of risk to the Warfighter.

TACTICAL DATA LINK TEST ENTRANCE CRITERIA

Table 1 shows the mandatory entrance criteria for entry into a TDL test.

Table 1. TDL Test Entrance Criteria

ITEM TDL TEST ENTRANCE CRITERIA TYPE

1 Request for Information ALL 2 Security Classification Guide ALL 3 MRTFB Fee (for Systems Undergoing System/NR KPP Certification) JIT 4 Service Level Testing/Standards Conformance Test Results JIT, CIT 5 JCIDS Documentation, Certified by the Joint Staff JIT 6 Bit-Level Implementation Data ALL 7 POAM and Integration and Communications Checks JIT, CIT

LEGEND:

ALL

CIT

JCIDS

JIT

MRTFB

JIT, CIT, and SCT Combined Interoperability Test Joint Capabilities Integration and Developments System Joint Interoperability Test Master Range and Test Facility Base

NR KPP

POAM

SCT

TDL

Net Ready Key Performance Parameter Plan of Action and Milestones Standards Conformance Test Tactical Data Link

The following paragraphs provide details for each entrance criteria for entry into a TDL test:

• Request for Information (RFI). One of the most important documents leading to a successful JIT is the RFI form. This form is a checklist that provides the JITC TD and Distributed Testing Operations Center information necessary to start the preparation for TDL JIT, test procedure development, and network engineering. A completed RFI is required to include Points of Contact, Security Accreditation/Documentation, System Information, and Sensor Simulation/Stimulation requirements. It is the responsibility of the PTUC to ensure that the RFI is completely filled in and returned to JITC 100 days prior to the start of a TDL JIT.

• Security Classification Guide (SCG). All systems entering a TDL test should provide JITC with their SCG, which will allow the proper classification of the testbed and marking the network diagrams, test procedures, and reports. This document is due to JITC 100 days prior to a test event.

• Major Range and Test Facility Base (MRTFB) Fee. The JITC is an MRTFB facility in accordance with DoD Directive 3200.11, Enclosure E.2.4. As an MRTFB facility, JITC is financed through a combination of appropriated funds and user charges in accordance with DoD 7000.14-R. In accordance with these directives, JITC requires a participation fee of $14,000 to fund TDL JIT costs unique to programs that are currently experiencing an acquisition cycle or programs requiring an interoperability/NR-KPP certification. The fee provides funding for the analysis of JCIDS documentation to include research of TDL-related IE requirements, review of system implementation along with capabilities and limitations, development of TDL mission threads, and development of an integrated architecture traceability matrix. The participation fee is also applicable to legacy systems that have newly approved Joint Staff-certified documentation and systems with major software upgrades. Participation fees shall be coordinated through the JITC Action Officer responsible for the certification of the system and through the system’s Program Office prior to the system being nominated for a JITC test event.

This funding is due to JITC 100 days prior to a test event.

• Service Level Test (SLT). Interoperability evaluation requires results from

SLT. The SLT is scheduled and coordinated through the PTUC, and the results shall be delivered to JITC prior to entry into a TDL JIT. Table 2 shows the required documents that shall be submitted to JITC. The SLT results are provided to JITC 100 days prior to a test event.

Table 2. Service-Level Documentation Requirements

ITEM DOCUMENT REQUIREMENT

1 SLT Standard Compliance Certification Letter, Test Reports 2 Service Interoperability Testing Certification Letter (if applicable), Test Reports 3 Service-Level Trouble Reports 4 Service-Level Test Procedures and/or Test Plan and Data Recordings 5 Concept of Operations (if available) ADDITIONAL REQUIREMENTS (when applicable)

1 Service Difference Document/Approved RFEs 2 Platform Requirements’ Specification and Platform Implementation Difference Document 3 Bit-Level Implementation File

LEGEND:

RFE Request for Exception SLT Service Level Test

NOTE: At the discretion of JITC, systems that do not meet JIT entrance criteria or provide required Service-level documentation may be allowed to participate as a SUT during a TDL JIT.

• JCIDS. The JITC requires SUTs, through their respective Service PTUC, to provide valid, certified J-6 documentation prior to entry into a TDL JIT event.

Without approved Joint Staff documentation, JITC is unable to provide a Joint Interoperability Test and Evaluation Support Memorandum.

• Bit-Level Implementation. Bit-level implementation identifies the information that a system exchanges on a TDL. A bit-level implementation can be submitted to JITC in any format (the preferred media is eSMART), as long as it identifies the implemented functional areas and list of messages, by message use, that include transmit and receive codes associated with each Data Field Identifier/Data Use Identifier (DFI/DUI), DUI/Data Identifier (DI) Name, DI Bit Code, and DUI/DI. (When submitting bit-level implementation for USMTF messages, details shall include Field Format Index Reference Number Field Use Designator, Message mandatory sets, segments, fields, and data items. Additional requirements include the use of conditional and operationally determined sets/segments/fields/data items).

Note: Without bit-level information, JITC is unable to issue a Standards Conformance Certification Letter.

• Plan of Action and Milestones (POAM). The POAM defines the actions and responsibilities of JITC, SUTs, and PUs necessary to conduct a TDL JIT.

The POAM will provide network configuration diagrams, IP addresses, and Voice over IP phone numbers for integration, dry-runs, and test conduct.

Prior to a TDL JIT event, a POAM will be drafted and published to each Service PTUC. The PTUCs will review, edit as applicable, and return. The JITC will redistribute final copy, and PTUCs will sign and return it to JITC.

Service PTUC signature on the POAM is mandatory for entry into a TDL JIT.

Appendix D contains an example of a POAM.

• Additional Requirements. The following documents may also be submitted to JITC for test planning purposes, when available:

o Service Difference Document (SDD). The SDD once approved and/or developed will define the difference between the MIL-STD requirements and specific Service TDL requirements to fulfill the Services and national data link philosophy and operational needs. Each SDD shall be reviewed and approved by the Joint Multi-TDL Configuration Control Board.

Approved SDD requirements shall become part of the current MIL-STD testing baseline and shall be considered in developing certification requirements and analyzing test results for the platforms of that Service.

The JITC and Joint Analysis Review Panels (JARPs) will consider the approved SDD requirement when determining whether to certify a TDL system.

o Platform Requirements Specification (PRS) and Platform Implementation Difference Document (PIDD). The PRS shows the intended individual platform TDL protocol and bit-level implementation data. The PIDD documents the planned deviations from the protocols and provides justification for the deviations. The JITC will consider the approved PIDD requirement when determining whether to certify a TDL system.

TEST SCHEDULING

Joint Interoperability Test. The JIT scheduling is coordinated between JITC and participating S/As and PTUCs. The PTUCs maintain schedules for their respective SUTs and PUs. The JITC publishes schedule changes quarterly to the PTUCs for review. The detailed test schedule specifies the JITC TD, type of test, test dates, JARP dates, JITC TD, supporting Test Lead, PTR due dates, test participants, and interfaces being tested. Service PTUC and JITC are the only entities authorized to change the schedule. Systems that want to participate in a JIT should contact the respective S/A PTUC. Contact JTC4 at <disa.huachuca.jt.list.tdl@mail.mil> for additional information.

Table 3 is an example of the JIT test schedule.

Table 3. Example JIT Test Schedule

JIT 18-04

TEST DIRECTOR

TEST LEAD

ASSISTANT TEST LEAD N/A

TEST LOCK DATE 1 MARCH 2018

DISTRIBUTE REQUEST FOR INFORMATION 1 MARCH 2018

REQUEST FOR INFORMATION DUE 8 MARCH 2018

INTEGRATION CHECKS 29 MAY–1 JUNE 2018

DRY RUNS 4–8 JUNE 2018

TEST CONDUCT 11–22 JUNE 2018

TEST HOURS 1200–2000 ZULU

PTRs DUE 16 JULY 2018

JARP 31 JULY–2 AUGUST 2018

SUT CWL LOCATION FWD 11 11B 16 JREAP OTHER

Aegis BL 7.2.2 Dahlgren, VA 11/16/16 X X C THAAD TFCC 6.0.0 Huntsville, AL X B/C LMMT 2.1 San Diego, CA X X C MH-60 v.SCS-18 Patuxent River, MD X

E-2D Hawkeye Patuxent River, MD Conc.

Ops X X

Aegis 9.C1.1.3.1E Dahlgren, VA 11/16/16 X X C

PARTICIPANTS

JITC BOSS Fort Huachuca, AZ X JITC TIGER Fort Huachuca, AZ X USAF ADSI Langley AFB, VA 16/16 X C USAF BOSS Langley AFB, VA X USAF MLST3 Langley AFB, VA X USMC CDLS Camp Pendleton, CA X C USN MLST3 San Diego, CA X

LEGEND:

ADSI

AFB

AL

AZ

BOSS

CA

CDLS

Conc.

CWL

FWD

JARP

JIT

JITC

JREAP

Air Defense Systems Integrator Air Force Base Alabama Arizona Battlefield Operational Support System California Common Data Link System Concurrent Commander’s Watch List Forward Joint Analysis Review Panel Joint Interoperability Test Joint Interoperability Test Command Joint Range Extension Application Protocol

LMMT

MD

MLST3

N/A Ops

PTR

SUT

TFCC

THAAD

USAF

USMC

USN

VA

Link Monitoring and Management Tool Maryland Multi-Link System Test and Training Tool Not Applicable Operations Preliminary Trouble Report System Under Test THAAD Fire Control/Communications Terminal High Altitude Area Defense United States Air Force United States Marine Corps United States Navy Virginia

Combined Interoperability. The CITs are scheduled through the CCIB process.

Systems that are ready for a combined test are nominated by the respective country to the CCMD Desk Officer during a CCIB. The CCMD Desk Officer will prioritize the country’s systems and request a test from JITC. The JITC can conduct one mission-funded CIT per year and additional tests on a reimbursable basis. The CIT system’s schedule will be posted on the JIT/CIT schedule (see Table 3). Contact JTC4 at <disa.huachuca.jt.list.tdl@mail.mil> for additional information.

Standards Conformance. The SCTs can be scheduled through JTC4 directly.

To schedule a standards conformance test, provide a statement of work to JTC4, and the branch will provide a POAM that will include a rough order of magnitude cost estimate. The schedule for the test can be negotiated to meet the program needs.

Contact JTC4 at <disa.huachuca.jt.list.tdl@mail.mil> for additional information.

RESULTS

Joint Interoperability Test. For systems being tested for NR KPP requirements during a JIT, JITC will issue a test report and a TDL Joint Interoperability Test and Evaluation Support Memorandum. The report will contain detailed test methodology and results.

The memorandum will support platform Joint Interoperability Test Certification and will contain a summary of the test results. For systems being tested in a JIT without a certified NR KPP, JITC will issue a test report and a TDL Standards Conformance Certification Memorandum that summarizes the system’s conformance to the tested standards.

Combined Interoperability Test. For systems being tested for combined U.S./(country) interoperability requirements, JITC will issue a test report that will identify capabilities and limitations that affect interoperability on TDL networks.

Standards Conformance Test. For systems being tested for standards conformance, JITC will issue a test report and an SCT Certification Memorandum. The test report will contain detailed test results and test methodology. The certification memorandum will contain the level of conformance and a summary of the test results.

A-1

APPENDIX A

ACRONYMS

3PS Third Party Source

AC Alternate Controller ACK Acknowledgement ACT Action ARP Analysis Review Panel ATC Authority To Connect ATC-Gen Automated Test Case Generator ATO Authority To Operate

BPS Bits Per Second

C2 Command and Control C4I Command, Control, Communications, Computers, and Intelligence CANTCO Cannot Comply CANTPRO Cannot Process CaT Capability Team CC Current Controller CCBD Configuration Control Board Directive CCIB Command and Control Interoperability Board CCMD Combatant Command C-E LCMC Communications Electronics Life Cycle Management Command CIB Common Interactive Broadcast CIBS-M Common Integrated Broadcast Service – Modules CIT Combined Interoperability Test CJCSI Commander Joint Chiefs of Staff Instruction CLEW Conventional Link 11 Waveform CMF Common Message Format CMP COE Message Processor COE Common Operating Environment CUS CIB Uplink Site

DAA Designed Accrediting Authority DAMA Demand Assigned Multiple Access DCM Data Collection Matrix DFI Data Field Identifier DI Data Identifier DIS Distributed Interactive Simulation DMTD Data Message Transfer Device DNCS Data Net Control Station DoD Department of Defense

A-2

DoDI Department of Defense Instruction DR Deficiency Report DREN Defense Research and Engineering Network DTOC Distributed Testing Operations Center

DUI Data Use Identifier DX Data Extraction

EMCON Emission Control

FFIRN Field Format Index Reference Number FMWG Format Mapping Working Group FOC Full Operational Capability FUDN Field Use Designator Number

GINS Global IBS Network Servers GTN Global Track Number

HPCMPO High Performance Computing Modernization Program Office

IAW In Accordance With IBS Integrated Broadcast Service IBS-A IBS-Alternate Paths IBS-N IBS-Network IBS-NS IBS-Network Services ICD Interface Control Document ICP Interface Change Proposal ID Identity IDD Interface Design Document IE Information Exchange IER Information Exchange Requirement IFF Identification Friend or Foe IFTU In-Flight Targeting Update IP Internet Protocol IRS Interface Requirements Specification ISP Information Support Plan ISR Intelligence, Surveillance, and Reconnaissance IT Information Technology ITS Interoperability Testing Syndicate IU Interface Unit

JANETT Joint Analysis Net-Centric Evaluation Testing Toolkit JARP Joint Analysis Review Panel JCIDS Joint Capabilities Integration and Development System JIT Joint Interoperability Test JITC Joint Interoperability Test Command

A-3

JITP Joint Interoperability Test Plan JMETC Joint Mission Environment Test Capability JMTCCB Joint Multi-TDL Configuration Control Board JMTOP Joint Multi-TDL Operating Procedures JNOC Joint Distributed Test Network and Operations Center JPTR Joint Preliminary Trouble Report JREAP Joint Range Extension Application Protocol JTC4 JITC Data Links Branch JTDL Joint Tactical Data Link JTIDS Joint Tactical Information Distribution System JTT Joint Tactical Terminal JU JTIDS Unit

KHz Kilohertz

LOS Line of Sight

MFL Multi-Function Laboratory MIDS Multifunctional Information Distribution System M-II Mandatory Requirement Implemented Incorrectly MIL-STD Military Standard MIN IMP Minimum Implementation M-NI Mandatory Requirement Not Implemented MOA Memorandum of Agreement MRTFB Major Range and Test Facility Base

N/A Not Applicable NACK Negative Acknowledgement NATO North Atlantic Treaty Organization NETOPS Network Operations NEW Network Enabled Weapons NPG Network Participant Group NR KPP Net Ready Key Performance Parameter NSA National Security Agency NSS National Security Systems

O-NI Optional Requirement Not Implemented OPR Office of Primary Responsibility OTA Over the Air OV Operational Viewpoint

PIDD Platform Implementation Difference Document POAM Plan of Action and Milestones PPLI Precise Participant Location and Identification PRS Platform Requirements Specification PTR Preliminary Trouble Report

A-4

PTUC Participating Test Unit Coordinator PU Participating Unit

R5 Reissue 5 RAFT Requirements Analysis Framework for Test RFE Request for Exception RFI Request for Information RST Realistic Test Scenario S/A Service/Agency SATCOM Satellite Communications SCG Security Classification Guide SCT Standards Conformance Test SDD Service Difference Document SDREN Secret Defense Research and Engineering Network SEC Software Engineering Center SIPRNet Secure Internet Protocol Router Network SLEW Single Tone Link 11 Waveform SLT Service Level Test SSE Streaming Single Instruction Multiple Data Extension SUT System Under Test SV System Viewpoint SYSCON Systems Control

TD Test Director TDIMF Tactical Data Inter-computer Message Format TDL Tactical Data Link TDLIOT Tactical Data Link Interoperability Test TDP Tactical Data Processor TDS Tactical Data System TENA Test and Training Enabling Architecture TIDP-TE Technical Interface Design Plan – Test Edition TIN Theater Interface Node TR Trouble Report

UHF Ultra High Frequency U.S. United States USA United States Army USMTF United States Message Text Format

VID VMF Integrated Database VMF Variable Message Format VoIP Voice over Internet Protocol VPN Virtual Private Network VTT VMF Test Tool

WIFT Weapon In-Flight Track

A-5

XML Extensible Markup Language

A-6

(This page is intentionally left blank)

B-1

APPENDIX B

JOINT INTEROPERABILITY TEST METHODOLOGY

Based on system missions, and Link 11, Link 16, and Joint Range Extension Application Protocol (JREAP) message implementation analysis, Joint Interoperability Test Command (JITC) will identify testable capabilities and defined mission threads.

The JITC will then develop scenarios comprising executable test events based on the implementations of the Systems Under Test (SUTs), participating systems, and implementation requirements in Military Standards (MIL-STDs). The JITC will also test all existing category 1 and 2 Trouble Reports (TRs) against the SUTs, as applicable, to verify whether the problems still exist and to identify any additional operational impacts.

The SUTs that do not have Joint Staff-certified requirements documented will be tested for the transactional requirements for implemented functional areas.

The test event conditions will evaluate information exchanges according to the transactional requirements defined in the applicable standard. Each transaction will either be manually executed or automatically executed to result in the applicable Link 11, Link 16, and JREAP message exchange.

The JITC will use the Automated Test Case Generator (ATC-Gen), a Link 16 web service that interacts with SUTs, to generate test cases that stimulate behavioral sequences in accordance with MIL-STD-6016. The ATC-Gen will be used to test correlation/decorrelation, Identification Friend or Foe/Selective Identification Feature difference messages, Mode 5 with Link 16, and Network Enabled Weapons.

RESULTS AND ANALYSIS

Problem Identification Procedure. The JITC and Service/Agency (S/A) analysts will review all aspects of the test and identify problems in Preliminary Trouble Reports (PTRs).