EC (ses ) 18 Jan 2007 TACTICAL DATA LINK 1 CORE DEC ARCHITECTURE AND POLICY EXECUTIVE SUMMARY

Transcription

1 EC (ses ) 18 Jan 2007 TACTICAL DATA LINK 1 CORE DEC ARCHITECTURE AND POLICY EXECUTIVE SUMMARY 1. Tactical Data Link (TDL) networks provide the specialised information infrastructures that underpin low time latency 2 Shared Situational Awareness and Command & Control (SSA&C2). The NATO family of TDL currently provides the bulk of the UK s Joint Data Network 3 (JDN) capability and underpin the compilation of the various local and theatre near real-time tactical pictures. Extraction of TDL-borne information into Internet-Protocol (IP) based operational networks, and vice-versa, is the subject of ongoing research and is therefore currently outside the scope of this policy. 2. Participation in TDL networks has a significant Cost of Ownership (COO) across all Lines of Development (LoD). All involved with the acquisition of platforms must factor in these costs and, via the Data Link Network Acquisition Authority (DLNAA) and GII Capability Planning Group 4, ensure that they are reflected in Balance of Investment (BoI) decisions and the total COO of this capability. Platform implementation options are to support coherent network capabilities and also examine support strategy synergy (with other platforms) covering repair, spares and Integrated Logistic Support (ILS). 3. The entry into service of the Carrier Strike and Deployed Operating Base (DOB) Capability in 2018; embracing the CVF, the Joint Combat Aircraft (JCA) and the Maritime Airborne Surveillance and Control System (MASC) will represent a quantum increase in capability and interconnectivity, providing a focus and target date for the UK TDL migration to the family of J- Series systems to enable a Network Enabled Capability (NEC) solution for tactical platforms. By that date, all UK TDL-fitted platforms will fulfil their near real-time data exchange requirements using J-Series message formats or through approved Gateways. However, the use of Link 11 by NATO and potential coalition partners is expected to continue for the foreseeable future. This factor is to be considered by UK platforms to maintain wider interoperability. 4. TDL Interoperability 5 for in service platforms is documented using the Through Life Interoperability Planning (TULIP) 6 and future capabilities are likely to be documented using the interoperable Systems Management and Requirements Transformation (ismart) tool, a development of TULIP that may be mandated 7 by the DLNAA and the Integration Authority (IA). 5. The DLNAA will play a key role in the implementation of this policy and TDL architecture and has the authority to grant exemption for non-compliance. Any non-compliance is to be specifically authorised by the DLNAA. 1 Previously known as the Tactical Information Exchange Networks Core DEC Architecture and Policy, Ed 2 2 Less than 15 seconds 3 Includes TDL, IBS, WAN, Gateways, Wideband Networking Waveform (WNW) and air comms. 4 CPG replaces CWG under Acquisition Change Programme. 5 In this context, interoperability is the ability of individual elements within a force to exchange tactical data by electronic means with sufficient timeliness, relevance, quantity and compatibility to enable the commander of the force to make the best use of the sensor and weapons capabilities under command. 6 Mandated in JSP Dependant on on-going assessment by IA 1

2 BACKGROUND 6. The Joint Capabilities Board established a high level Equipment Capability Customer (ECC) goal for an integrated Equipment Capability of Network Programmes, Network Ready Platforms and Integrated Headquarters 8. JSP 777 Network Enabled Capability captures this intent to invest in networks as a means of maximising the capability inherent in current and future platforms. Network Enabled Capability (NEC) encompasses the ability of platforms 9 and Command & Control (C2) capabilities to: a. Exploit Shared Situational Awareness (SSA) and collaborative C2. b. Communicate and understand the commander s intent. c. Deliver Battlespace Management (BM) in order to create Decision Superiority (DS) and the delivery of synchronised effects in the Joint and multi-national Battlespace. 7. TDL architectures are utilized in the real-time and near real-time tactical environment to exchange sensor-derived information between platforms for SSA and C2, building into the Recognised Air Picture (RAP) and other tactical pictures. Additionally TDLs contribute significantly to the conduct of tactical Battlespace Management by C2 platforms in the air and maritime environments. Extraction of TDL-borne information into the operational network infrastructure and subsequent incorporation into the Joint Operational Picture will require Internet- Protocol gateways to be developed; this is the subject of ongoing research and is therefore outside the scope of the current policy. 8. Acquisition of TDL has historically been platform-centric and the true costs of ownership, interoperability and important network-centric issues such as implementation and gateways have been overlooked. Lessons identified in recent operations and exercises have demonstrated that the penalty of this approach has been the realisation of incoherent near real-time tactical information exchange architectures, which hamper the prosecution of the tactical battle. DEC (CCII) is charged with delivering a coherent and interoperable Information Infrastructure. This paper provides Core DEC direction upon how this will be achieved in the TDL domain. AIM 9. To mandate a Core DEC policy framework and outline TDL architecture in order to shape procurement and Through Life Capability Management of the TDL equipment capability. VISION 10. A coherent and flexible near real-time information exchange environment that supports C2, decision making, shared situational awareness and weapon control through the minimum use of data translation interfaces and gateways, characterised by: a. High capacity. b. Security. 8 D/CM(IS)2/1 (106/02)29 May Including sensors and weapons. 2

3 c. Supporting Combat ID. d. Survivability and resilience. e. Latency sufficiently low as to assist prosecution of the real-time tactical battle 10. f. Seamless to the user. g. Connectivity from sensors to effectors, via decision makers, overlaid with C2 directives. h. Joint and multi-national interoperability. GOALS OF TDL POLICY AND ARCHITECTURE 11. The establishment of a TDL policy and architecture will maximize the return on the UK s significant investment in platform capability. It will improve the interoperability of existing and evolving capabilities whilst supporting interoperability with our Allies in accordance with DSG05. The philosophy adopted is pragmatic rather than prescriptive; any conflict resolution will be conducted under the auspices of the Core DEC, DEC (CCII), through the GII CPG and by the DLNAA. The Policy goals are to: a. Establish a single, seamless message standard for the exchange of near real-time tactical data between UK platforms in all environments, and for operations with US, NATO and potential coalition partners 11. b. Improve Interoperability by using standard messages and standardized data elements, adoption of a standardized process 12 and by creation and maintenance of configurationcontrolled documentation. c. Reduce proliferation and duplication of information infrastructures. d. Improve information dissemination through effective and managed use of Gateway technologies. e. Allow the controlled introduction of emerging technology into the Joint and multinational operating environments. f. Improve the tactical effectiveness of TDL, providing a robust structure to cater for the information exchange requirements of all UK TDL-equipped platforms. 10 This includes anti-missile defence at the operational and tactical levels of command. 11 The J-Series message format compatible family of TDL, hereafter referred to as J-Family message formats has been selected by the UK, US and NATO as the vehicle to achieve this goal. This family includes J-series Link 16, K-series VMF and F-series Link 22 message formats. However, L11 will continue to be employed by legacy platforms. 12 TULIP for in service TDL applications and as mandated by IA for future applications. 3

4 ASSUMPTIONS 12. UK TDL will be based on mandated standards wherever applicable: UK doctrine requires interoperability in joint and multi-national operations with allies and coalition partners, with TDL standards mandated by the DLNAA and maintained by the IA. 13. The MOD Policy for Data Links 13 and the DLNAA drive to promote systems that are net ready, continue to underline the need for management of digital data exchange in support of the production of a family of common operational pictures and the conduct of digital command and control. All will require information exchange between new and in-service Command, Control, Communications, Intelligence, Surveillance, Reconnaissance and Weapons platforms for the foreseeable future. 14. Character-based links (such as those using Allied Data Publication - ADatP3) will continue to be used for non real-time information exchange in Command and Battlespace Management (CBM) Applications and Information Services. However, information exchange via TDLs and BOWMAN will remain the backbone of real-time and near real-time tactical C2 systems in the Battlespace for the foreseeable future. SCOPE 15. The policy encompasses the exchange of digital information between real-time mission systems via bit-oriented 14 information exchange networks, such as the family of NATO TDLs. It is focused on the requirement to enhance the interoperability of National and NATO forces through the migration towards a smaller number of complementary information exchange systems, the standardization of message formats and data elements and interfaces/gateways between these systems. 16. The policy addresses the TDL architecture in the short to medium term, including the documentation required to support interoperability. It is linked to ongoing work in the MOD Research Programme and the IA support work in the wider JDN area. A Glossary is provided at Annex A with a list of Abbreviations at Annex B. DESIRED END-STATE 17. The desired end-state is that by the time of the introduction of JCA into UK service, all UK TDL-fitted platforms will fulfil their near real-time data exchange requirements using J-Series Family message formats or approved Gateways. This UK migration to J-Series Family of TDL mirrors that of both the US and NATO. 18. The policy is based on the NATO Strategic Commanders data link migration strategy 15, pays due cognizance to the US Joint TDL Management Plan and US transformational efforts 16 in the TDL field. It is designed to be sufficiently flexible to embrace new platform capability requirements as they emerge. Interoperability will be documented using the TULIP process for inservice TDL platforms. For all future TDL/JDN equipped platforms, interoperability is likely to be 13 2* CBM EG endorsed MOD Policy for Data Links DGInfo/DCBMJ6/Data_Link_Policy dated 24 Nov Bit oriented - information is coded at the binary level and machine-readable only, rather than in character based man readable formats including ADatP3, USMTF or OTHT-Gold. 15 The NATO Bi-Strategic Commander s Tactical Data Link Migration Strategy. 16 US TDL Transformational Definition Document, Apr

5 documented using the interoperable Systems Management and Requirements Transformation (ismart) tool, a development of the TULIP process that may be mandated by the DLNAA. IMPLEMENTATION OF POLICY 19. In addition to receiving information for their own purposes, almost all platforms participating in TDL operations will contribute information to the networks, for example by reporting track information and their own position. In order for platforms to act in a net-centric manner it is essential that the networks can be managed coherently. This requires selection of platform implementations that recognise the need for such activities and ensure all Information Exchange Requirements (IER) are adequately captured in the early stages of the CADMID cycle 17. Equally, there are overarching costs associated with ownership 18 which will be the responsibility of the Core DEC, DEC (CCII), the DE&S and the lead FLC. 20. The DLNAA. The DLNAA 19 have recognised that participation in a TDL network has associated overheads. New network participants or any new IER will inevitably impact on the network 20 as a whole and may well require change in other platforms TDL implementation to achieve the desired information exchange 21. The goal must be to provide a capability that is coherent in network as well as platform terms; the mechanism for achieving this coherency is the DLNAA. The DLNAA is a federation of DEC CCII, IA6, TDL IPT and CBM-J6 (Strategic User) and JDLMO (Joint User), accountable to the 1*NEC/ISR Steering Committee. 21. ECC platform desk officers, IPT Leaders and their staffs are to ensure that the needs and aspirations of existing UK TDL users arising as a consequence of any new requirements are addressed and documented within Platform Documentation. Adequate provision is to be made within Initial Gate (IG) and Main Gate (MG) submissions to identify and ensure the availability of funds to pay for any required changes, both to existing network participants and for any increase in the overall cost of network ownership 22. DLNAA advice is to be sought to identify financial, technical and capability implications. 22. All platforms with a requirement for a TDL capability shall implement the appropriate TDL architecture and Standards 23 as detailed in paragraphs If alternate TDL are proposed for implementation, or TDL capabilities required to support the Network are not proposed for platform implementation, this shall be justified to, and agreed by, the DLNAA and the DEC(CCII) Core TDL desk officer. 23. Information Exchange Requirements (IER). ECC desk officers are to include IERs in the 17 Concept, Assessment, Demonstration, Manufacture, In-Service, Disposal: the Smart Acquisition Process. 18 For example centralised configuration management of standards, TNDS support, system-wide interoperability testing and, in the case of JTIDS/MIDS, JTIDS frequency clearance with Civil/Federal Aviation Authorities. 19 Empowered by the MOD Policy for Data Links dated 24 Nov 04 & Std DL Acquisition Procedures Letter - EC/14/03/08/32 dated 11 Jul At the very least on the consumption of bandwidth, which may not be available without prioritisation. 21 For example, expansion of the E-3D message implementation to enable C2 of CAS missions. 22 Three examples of costs falling outside of a platform: - Interoperability testing requires participation on both sides of the interface, not just the new joiner. The cost of this activity must be recognised and provisioned as early as possible within the acquisition cycle. - ASTOR will present ground tracks to the MIDS/L16 surveillance pool, very few UK platforms can display ground tracks so change will be required to utilise this newly available information. - Network design tools frequently require change to allow for new participants and transmission protocols. 23 IA6 is responsible for configuration management of UK TDL Standards, representing the UK as Head of Delegation to the NATO C3 Board Data Link Working Group and acting as custodian of UK TDL standards documentation. 5

6 description of the required TDL capability. Guidance in the preparation of IERs can be obtained from the JDN desks within DEC(CCII), the Requirements Managers in the TDL IPT and the IA. Information Exchange analysis is an integral part of the interoperability process. A database of IER and IDF and associated analysis toolset has been established under a proposed UK architectural Framework ismart Requirements & System of System Transformational (afirst) Team. Use of such a validated set of Information Definitions 24 (IDFs) is likely to be mandated for all future TDL equipped platforms. 24. Interoperability. Understanding and demonstrating interoperability is key to a successful national TDL capability. The DLNAA s chosen process for achieving in-service TDL interoperability is the application of the TULIP process currently mandated in JSP 602. Enhanced developments of TULIP are now available 25 and new platforms implementing TDL will be expected to apply an enhanced process under guidance of the DLNAA, throughout the CADMID cycle 26. All TDL enabled systems are to maintain their representation in the MOD architecture repository, hosted by the IA. Interoperability testing 27 is a mandatory requirement and Ds of EC through the Defence Planning process shall, in conjunction with their platform IPTs, make provision for such testing on behalf of all participants in the interface. The introduction of DLNAA s TDL Interoperability Coherence Assurance (IOCA) programme will provide a method of verifying interoperability through process audit and practical/live validation. This Networthiness process is mandatory for all new UK platforms implementing TDL 28. Meanwhile, platform URD/SRDs are to explicitly recognise the network-centric requirements 29 inherent in TDL operations. 25. In service platforms are to recognise that maintaining interoperability will often require change in order to support the wider TDL community. They are to undertake such TDL changes/implementations in a timely fashion as directed by the DLNAA. Charges are to be provisioned from platform funds as a COO issue. Only in exceptional cases will these platform changes be centrally funded. 26. In service platforms still planned to be in service after the scheduled introduction of JCA are to either: a. Secure programme funding to provide a technology upgrade/refresh in order to achieve J-Family compliance by; (1) TDL sub-system replacement (hardware, software or firmware), or (2) Implementation of a DLNAA-approved Gateway. b. Obtain a non-compliance waiver from the DLNAA These validated IDFs form the foundation for ismart and are harmonised between the UK and US. 25 eg ismart process for TDL. 26 Use of TULIP applies to all TDL, inclusive of Links 11, 16, 22 and VMF, and may in future be expanded to other data links. 27 Defence Policy for TDL Interoperability Testing Sep Direction on the scope and conduct of Networthiness Testing is under development, and will be issued separately. 29 A statement and document reference confirming NAA acceptance of TDL implementation is to be included in Main Gate BCs. ismart and Interoperability are to be addressed in URD/SRDs. 30 This course of action will not be permitted except in exceptional circumstances as it will lead to unconnected platform islands adrift in the NEC sea. 6

7 TDL ARCHITECTURE 27. The following J-Series Family TDL message formats shall be implemented by UK platforms to meet the desired end-state in accordance with their roles and IER: a. JTIDS/MIDS Link 16. b. Tactical BLOS TDL (Link 22 and/or Link 16 Joint Range Extension). c. Variable Message Format. Legacy TDLs will continue to be maintained until platform OSDs or upgrade/migration paths to J- series family TDLs have been identified. These legacy TDLs include: d. Link 11. e. Satellite TDL 31. f. TACFIRE/AFAPD. g. Link 1 and IJMS In addition to these message formats, there is an enduring requirement for Network oversight regardless of transmission medium, addressed by DEC (CCII), which includes: a. Network Planning, Design and Dissemination. b. Network Management and Monitoring. c. Spectrum Management and Frequency Clearance Compliance monitoring. d. Network (and platform) Fault-Finding and Rectification. These functions are vital to provide and maintain effective utilisation of networks, and contribute an overhead in terms of personnel, equipment and facilities to the overall COO of the UK s TDL capability. 29. JTIDS/MIDS Link 16. JTIDS/MIDS Link 16 shall be the primary line of sight (LOS) TDL for all tactical maritime, land, air and Joint assets 33. Platforms with a C 2 responsibility will need to implement Time Slot Re-allocation (TSR) in both centralised and decentralised modes, ideally by 2009, to maintain full interoperability with US platforms and those of other allies. 30. Tactical Beyond Line of Sight (BLOS) TDL. Participants in BLOS networks will be determined by CONEMP and IERs that have yet to be captured in URDs. DEC (CCII) has a funded 31 Satellite Tactical Data Link (STDL), a Link 16 based information infrastructure, implemented on a number of RN platforms as a UK-only BLOS data link. 32 Link 1 and Interim JTIDS Message Set (IJMS) are legacy NATO TDLs which are being retained to allow continued NADGE interoperability. 33 For current in-service air manoeuvre assets, it is accepted that Link 16 may not be practicable and/or affordable and hence may not be implemented. In such circumstances the use of gateways is to be investigated. 7

8 programme in the Assessment Phase to evolve the equipment solution to close this capability gap and to provide some elements of this capability. Candidate solutions for the BLOS TDL include Link 22, the US Joint Range Extension Application Protocol 34 (JRE-AP) programme or, possibly, a mix of these. The TBLoS programme was originally approved for TBLOS capability for T23, T42 and CVS naval platforms, however, a key stakeholder review of requirements conducted in the first half of 2005 highlighted balance of investment challenges that require the programme to select an equipment solution that can accommodate emerging capabilities such as Carrier Strike. The assessment phase of the programme will have to address these challenges. 31. Variable Message Format. Variable Message Format (VMF) is a bit-oriented and media independent message standard. VMF has been developed by the US primarily for land tactical intranet use and is a message standard that can operate over any digital-capable radio frequency (RF) broadcast or point-to-point system. It has no embedded communications protocols and is built to operate in an Open Systems Interconnection-compliant environment. 32. Data Modem-enabled TDLs. In an ideal world all platforms would be able to exchange information via a single, universal data link, which would bridge the air/ground information infrastructure gap 35. This is unlikely to be a practicable situation for the foreseeable future on technical and cost grounds; therefore in the short to medium term, data exchange between airborne and ground-based assets will build upon existing platform implementations. Work is in hand within the EP and the ARP to scope the issues associated with this approach including potential solutions for interoperability with BOWMAN-based ground networks. New implementations in this environment shall provide the capability to undertake information exchange with existing platform implementations. 33. Gateways. The JDN Roadmap 36 recognises the need for Gateways between dissimilar infrastructures as a potential incremental solution to achieving wider interoperability. Gateways shall be implemented only to satisfy agreed IERs, in support of defined doctrine and CONOPS, where the IERs cannot be supported by a single infrastructure. DLNAA advice and DEC (CCII) approval is to be sought in instances where gateway technology is envisaged. The DEC CCII JDN Backbone is a funded programme in the Concept phase to connect and transfer real-time and near real-time tactical data between existing tactical data networks, with the initial phase providing inter- TDL gateways. 34. Data Forwarding. In the context of this policy, Data Forwarding as understood within the TDL community is considered as a subset of the Gateway function. Data Forwarding (in TDL terms) shall be implemented for coherent information exchange between the Link 11, JTIDS/MIDS Link 16, Tactical BLOS networks and Integrated Broadcast System (IBS). It is intended that Data Forwarding functionality should be included in all C2 Platforms with multi-link requirements 37. Work is underway within the Research Programme and the EP under the auspices of the DLNAA to clarify gateways issues and define those that are required. 34 Mil STAN The USAF position is to employ Link 16 for all functions; however, the other US Services are developing VMF, as a replacement for TACFIRE/AFAPD, for use in Close Air Support and other air-ground functions. Due to limitations in the use of Link 16, particularly within Europe, VMF is the selected UK DL format for data exchange at the air/land interface in support of ground attack operations. The UK will explore the application of ismart to VMF implementations based on MIL-STD JDN Roadmap Issue 2 dated 24 May 2006 (STA/R/580/1/Issue 2). 37 It is recognised that the E-3D would need to introduce a data forwarding capability to comply with this requirement which is unaffordable at this time. Further work is necessary to determine whether such a capability is required within the network architectures likely to be fielded operationally within the aircraft s remaining service life. 8

9 35. Link 11. Link 11 is currently fitted for the purpose of BLOS and LOS tactical information exchange, particularly in the maritime environment. In future, LOS requirements will be met by JTIDS/MIDS Link 16 and BLOS requirements by the TBLOS data links. Platforms currently implementing Link 11 shall retain that capability for the conduct of operations with nations that will not be implementing JTIDS/MIDS Link 16. New platforms that intend to conduct integrated operations with non-link16 equipped platforms or nations shall also implement Link 11. Link 11 has served as NATO s principal BLOS near real-time tactical information exchange data link for many years. Due to advances in technology, principal NATO Nations and the US are migrating from Conventional Link Eleven Waveform (CLEW) to Single-tone Link Eleven Waveform (SLEW), providing significant performance benefits; the UK will also adopt this migration strategy 38 for all principal C2 platforms. The requirement to implement and support Link 11 (SLEW) to maintain interoperability with the US, NATO and other potential Coalition partners will extend for the foreseeable future TACFIRE/AFAPD. At present in the UK, tactical data exchange has been enabled on a number of platforms using the Improved Data Modem (IDM) utilising Tactical Fire Direction System (TACFIRE) and Air Force Application Program Development (AFAPD) message formats 40. Both TACFIRE and AFAPD formats are poorly documented, lack configuration control and are no longer supported by the USA. While TACFIRE/AFAPD over IDM does provide a costeffective method of data exchange, it lacks wider utility, and though adoption of such a solution will give like-platform interoperability 41, a TACFIRE/AFAPD implementation will not alone provide J- Family compliance Sensor Networks. Fused sensor data is being carried by TDL applications into the TDL networks augmenting TDL data and providing a more complete TDL picture. The UK is involved with several US programs and technology demonstrations 43 to permit exploitation of sensor data by the wider community. The TDL and wider Joint Data Network (JDN) communities are to ensure coherence and interoperability, to a maximum extent, between these complementary systems: a. Combined Land Air Sea Picture (CLASP). CLASP is an ISTAR concept for the provision of fuseable information, including target quality data, to a series of networks to allow effective Command & Control and precision engagement of time sensitive targets. This will be achieved by making optimum use of all available sensors, through secure collaborative networking. CLASP draws on the CEC, LISTENER and NEADS programmes 44. b. Single Integrated Air Picture (SIAP). The SIAP is a joint US services initiative to deliver common integrated air picture capability across operational maritime, land and air platforms. The SIAP initiative is being monitored by UK, France and Germany, and within the UK is informing a number of programmes including the DEC CCII and DEC ISTAR Air Picture Coherency initiative. 38 SLEW has a reversionary CLEW capability. CLEW and SLEW modes are incompatible. 39 At least until In essence, NATO standard V/UHF radios, Improved Data Modem (IDM), platform-specific AFAPD and TACFIRE implementations of the Apache helicopter and Jaguar GR3a aircraft. 41 Such as Apache Helicopter to Apache Helicopter. 42 To achieve compliance, an IDM that also supports VMF formats is required (currently IDM v3.04). 43 NCCT and AJCN technology demonstrators. 44 CEC Co-operative Engagement Capability; LISTENER ISTAR sensor integration; NEADS Networked Air Defence System. 9

10 POLICY MAINTENANCE 38. The introduction into service of the individual data networks that collectively comprise the Joint Data Network and overarching Global Information Infrastructure will be the physical basis on which NEC is developed. As improved TDL processes and technologies emerge these are to be embraced to support the delivery of NEC. This Core DEC TDL Policy will be reviewed and refined to ensure it retains both relevance and coherence. Updates will be issued periodically as-required. The Integration Authority will reflect the requirements of the Core DEC Policy on TDL within the JSP600 series. CONCLUSION 39. TDL are a cornerstone of NEC and provide much of the UK s fielded infrastructure to achieve the information exchange that is required for shared situational awareness and increased operational tempo. As Core DEC for the equipment line of development of the UK MOD's Information Infrastructure, DEC(CCII) holds responsibility for ensuring that all networks that contribute to delivery of NEC are coherent and interoperable. This state will not be achieved without adoption of common processes, standards and implementations by all TDL-equipped platforms. This policy document provides direction and guidance on the implementation of TDL capability in both in service and future platforms. 10

11 ANNEX A TO EC DATED 18 JAN 07 GLOSSARY For the purposes of this policy the following definitions and supporting information apply: Co-operative Engagement Capability (CEC). CEC is the first physical implementation of a true real-time multi-participant information exchange system. It is designed to allow US Navy Surface Action Groups (SAGs) and airborne elements to exchange integrated, fire control quality plot data in real-time, specifically to defeat high performance air breathing anti-ship missiles but also with enormous utility to create a high quality real time air picture. A CEC capability has been specified for the Royal Navy and could in future form the basis of joint composite tracking networks. Concurrent Operations. Concurrent operation is the process of communicating on two, or more, digital data links at the same time, as a participant. The concurrent operating unit exchanges all information held in its local data base, but remote information is not forwarded. Protocols of each link are adhered to by the concurrent operating unit. The local data base of a concurrent operating unit is the normal assimilation of data by that unit and includes local sensor data, local operator inputs, and data received and accepted into the local data base from a data link, e.g., ID or IFF/SIF data 44. Gateways. Gateways provide a means to exchange information between dissimilar, otherwise incompatible TDL systems. Gateways receive, translate, and then forward data between applicable TDLs whilst preserving the security and integrity of the data. A gateway consists of the communications mediums, message standards and message implementations used by each TDL system and software that translates between systems. (If, for example, a gateway is to provide interoperability between L16 and JRE-AP the gateway would consist of a complete L16 system, a complete JRE-AP system and software providing the gateway functionality such as ROBE). Gateways can provide additional capabilities not provided by the TDL system, such as BLOS capabilities for a LOS TDL system. a. Message Translation. This deals with both the data format (syntax) and its content or meaning (semantics). Gateways may translate between message standards and/or cross band (router and retransmission functionality) between different communications media. b. Data Forwarding. This is the process by which a message or sequence of messages received on one TDL are transformed to the appropriate message standard or message sequence for transmission on another TDL NATO STANAG 5616 Edition 3 dated 9 March A - 1

12 Figure 1- US Gateway Enabled TDL Architecture Future Links. A number of new Links may either enter service with or be encountered by UK forces in the future. The most significant are as follows: a. Variable Message Format (VMF). The bit-oriented Variable Message Format (VMF) being developed by the US is an emerging message standard 46 (K Series) that can operate over any digital-capable radio frequency (RF) broadcast or point-to point system. It has no embedded communications protocols and is built to operate in an Open Systems Interconnection compliant environment. In the US, VMF is currently employed predominantly at the tactical level in the Combat Net Radio (CNR) environment (HAVEQUICK I/II and SINCGARS) primarily for ground force connectivity. b. Link 22. Link 22 was developed under 7-nation collaborative development to create a secure, ECM resistant, medium-speed tactical data link for the exchange of real-time tactical and technical information between maritime units. Link 22 is being designed to utilise various communications media, including HF (2-30 MHz) and UHF ( MHz) fixed and frequency agile waveforms, however, the proposed UK initial implementation is currently limited to HF fixed frequency to provide a Beyond Land of Sight (BLOS) TDL. Link 22 provides a multi-networking capability and a set of connected Link 22 networks will be referred to as a Super Network. A single Super Network may comprise up to eight component networks. Most significantly, the Link bit F-Series message standard (STANAG 5522) is based on the Link 16 J-Series standard with some additional messages to manage the network s BLOS capabilities. Six nations are now maintaining the protocols through an International Project Office (IPO) that will support and assist national implementations. 46 MIL STD 6017 A - 2

13 c. ACCS-Wide Common Information Exchange Standard (AWCIES). AWCIES will provide a far more capable and secure replacement for Link 1 amongst NATO ACCS entities, although the external interface will remain as Link 1. Information Exchange Requirements (IER). Those categories of information that are to be exchanged between operational facilities in order to provide commanders with essential information for the conduct of operations. Integration. The act of putting together as a final item various components of a system in such a way that the combination of separate systems, capabilities and functions can operate effectively, singly or in concert, and without adversely affecting the other elements. Interoperability (IO). The ability of systems, units or forces to provide services 47 to and accept services from other systems, units or forces and to use the services so exchanged to enable them to operate effectively together. Interoperability in the TDL Context. The term Interoperability, in the context of the information exchange, means that a system, unit or forces of any service or nation can transmit data to and receive data from any other system, unit or forces of any service or nation and use the exchanged data to operate effectively together. Without interoperability, there is no point in having a communication system; consideration of interoperability is hence the key to the entire integration process. The level of interoperability achieved can be considered in a number of different layers. A large number of different aspects of the system must fit together in order that all the levels of interoperability are achieved. In addition to achieving the physical transfer of messages between platforms (Radio Frequency (RF) Interoperability), it is essential that the messages sent over the Link contain the data necessary to achieve the IER (Data Interoperability) and that they conform with the protocols defined for Link operation (Protocol Interoperability). The information contained in the messages must also complement the operational procedures defined for conducting the mission, task or battle. Finally, on reception, the information must be displayed and interpreted correctly by the receiving operators (Human Computer Interface (HCI) & Brain-to-Brain Interoperability) and, if appropriate, forwarded onto other near-real time networks in a correct and timely manner so that an entire force can share the same tactical information. J-Series Family of TDLs. The family of data links based on common data elements, consisting primarily of the J-Series data elements, J-Series messages, and the communications protocols and hardware for Link16, Link22 and VMF, as well as point-to-point, multi-point, and radio/satellite broadcast J-Series data link capabilities developed in the future. Link 11. Link 11 is a secure, netted data link operating on HF and UHF for the exchange of surveillance, combat weapons direction and battle management data. a. Conventional Link Eleven Waveform (CLEW). Data is transmitted in two 30- bit frames, each consisting of 24 information bits and 6 error detection and correction bits. The information message is essentially a 48-bit word. A frame is transmitted in parallel on 15 multiplexed tones. Diversity is available as required by identical transmissions or independent sideband. A 16th tone is reserved for Doppler 47 Services is taken to mean information, specifically in the form of digital data A - 3

14 correction. (1) Maximum achievable HF range is approximately 300 nm. b. Single-tone Link Eleven Waveform (SLEW). Data is transmitted in a message format consisting of an acquisition preamble followed by a header block, a number of data fields and an end-of-message (EOM) field. The preamble resolves automatic gain control (AGC), signal detection, synchronisation, Doppler requirements and equalisation. The header and data fields use digital procedures for error detection and correction (EDAC) to gain robustness. (1) SLEW should only be used if all Link 11 participants have the capability. If any one Link 11 participant does not have the capability to operate using SLEW, CLEW is be used. (2) SLEW has a reversionary CLEW capability. (3) Maximum achievable HF range is approximately 600 nm. Link 11B. Link 11B is a secure, point-to-point adaptation of Link11 passed over terrestrial bearers. Link Enabled. A TDL equipped platform that is capable of operating in a TDL network iaw laid down standards, protocols, and procedures. Its inclusion within the network does not detract from overall link efficiency. MIDS/Link 16. Link 16 is a secure, high-capacity, jam-resistant nodeless data link which uses the Joint Tactical Information Distribution System (JTIDS) or Multifunctional Information Distribution System (MIDS) transmission characteristics and the protocols, conventions and fixed-length message formats defined in STANAG 5516 and MIL-STD 6016C. Multi-National Operations. In any operation where US forces are committed, they are likely to have the preponderance of TDL-equipped assets, as well as the most capable systems. Whilst US doctrine emphasises the need for interoperability, especially with NATO, this requirement needs to work in both directions. UK TDL systems and standards are to be established, designed and maintained to ensure compatibility with the US and NATO forces. Net Ready. A platform that has been assessed to have undertaken all net-centric processes/steps iaw the DLNAA policy for Networthiness. Networthy. A Networthy platform is one in which network interactions are iaw laid down standards, meet CONUSE/procedural requirements and do not adversely affect the network. Network Enabled. A Network Enabled Platform is one that has the ability to originate, process, consume, pull or push mission-relevant information with other nodes/platforms/centers to the extent needed to achieve desired effects It can access, on-demand, the information, services, and the network in a standard manner A - 4

15 Platform Implementation. Each TDL has a specified set of messages for the exchange of data. Not all platforms will need to be able to implement and display the whole message set; for example, an air defence fighter aircraft is unlikely to need, or have the required processing and display power to interpret Link 16 messages pertaining to ASW track information. The decision on which messages to implement in each individual platform is, however, fundamental to successful net-centric TDL operations and this decision is to be supported by sound operational analysis and guided by Doctrine and Concepts of Employment and Use (CONEMP/CONUSE). Each platform is to implement the full range of messages relevant to its role; this will be particularly crucial for C2 units. Any TDL participant responsible for the formulation, dissemination or forward transmission of C2 data and instructions should be considered as part of the C2 chain and should thus be considered, in TDL terms, a C2 entity, with TDL functionality implemented accordingly. This is a separate issue to that of C2 authority and will apply whether or not the participant is a C2 unit in its own right. All platform implementations are to be regularly reviewed to ensure on-going effectiveness and interoperability to reflect changes in standardisation agreements, the operational environment and drive towards NEC. Platform Integration. The integration of a TDL into a platform can be a complex process, requiring changes to the host system that will allow it to initialise the terminal, to collect, format and pass information to the terminal, to process and display the data received and to generate appropriate alerts. If a modern TDL such as JTIDS/MIDS Link 16 is being retrofitted to an in-service platform, this can often require upgrading the processors, fitting control panels for the terminal and cryptographic equipment, and installing initialisation loading devices and very significant changes to the MMI. In the case of a small manned aircraft, this may lead to cockpit space problems and may impose significant payload and power supply challenges. A good integration can dramatically increase a platform's effectiveness, but, if the integration is poor, there is a risk that operators will be swamped with information, the crew s workload will increase and collective effectiveness will decrease. Tactical Data Link. TDLs are standardised communications links suitable for transmission of digital information between two or more locations to interface computerised C2 or weapon systems via a single or multiple network architecture and multiple communications media for near real-time exchange of tactical information. A - 5

16 ABBREVIATIONS ANNEX B TO EC DATED 18 JAN 07 ACCS AFAPD ARP AWCIES BLOS BM BOI CADMID CBM C2 CEC CID CLEW COO CPG CWG DF DLNAA DS ECC EP FLC GIG HCI IA IBS IDF IDM IER IG IJMS ILS IO IOCA IP IPO Air Command and Control System Air Force Application Program Development Applied Research Programme ACCS Wide Common Information Exchange Standard Beyond Line of Sight Battlespace Management Balance of Investment Concept, Assessment, Development, Manufacture, In-Service, Disposal Command and Battlespace Management Command and Control Co-operative Engagement Capability Combat Identification Conventional Link Eleven Waveform Cost of Ownership Capability Planning Group Capability Working Group Data Forwarding Data Links Network Acquisition Authority Decision Superiority Equipment Capability Customer Equipment Programme Front Line Command Global Information Grid Human Computer Interfaces Integration Authority Integrated Broadcast System Information Definition Improved Data Modem Information Exchange Requirement Initial Gate Interim JTIDS Message Standard Integrated Logistic Support Interoperability Interoperability Coherence Assurance Internet Protocol International Project Office B - 1

17 ISD ISR ismart ISSE J2CSP JCA JCB JDLMO JDN JOP JOCS JSP JTIDS JRE-AP LoD MIDS MG MTF MMI NADGE NEC OCD RAP RLP RMP SA SSA SIAP SLEW STDL SRD TACFIRE TDL TNDS URD VMF VoIP WNW In-Service Date Intelligence, Surveillance & Reconnaissance Interoperable Systems Management and Requirements Transformation Integration Services Support Environment Joint Command and Control System Programme Joint Combat Aircraft Joint Capabilities Board Joint Data Links Management Organisation Joint Data Network Joint Operational Picture Joint Operational Command System Joint Service Publication Joint Tactical Information Distribution System Joint Range Extension Application Protocol Line of Development Multifunctional Information Distribution System Main Gate Message Text Format Man Machine Interface NATO Air Defence Ground Environment Network Enabled Capability Operational Capability Demonstrator Recognised Air Picture Recognised Land Picture Recognised Maritime Picture Situational Awareness Shared Situational Awareness Single Integrated Air Picture Single-tone Link Eleven Waveform Satellite Tactical Data Link System Requirements Document Tactical Fire Direction System Tactical Data Link Tactical Network Design Station User Requirement Document Variable Message Format Voice over Internet Protocol Wideband Network Waveform B - 2