Baykar wants to have in-house datalinks because
1) They design their own avionics accordingly.
2) They have their own plans/performance goals for their assets that require datalinks tailored to match those goals. If you want to develop an unmanned fighter that can operate autonomously and create an autonomous wing from unmanned fighters, you want a datalink precisely optimized for that need. Aselsan's IVDL is in development in the scope of MMU project for the needs of KAAN. Aselsan will probably modify IVDL in line with Baykar's performance goals of unmanned fighter and wing autonomy if Aselsans IVDL is to be used on KE. Baykar used outsourced datalinks for TB2 and Akıncı in the past, but switched to in-house datalinks after sometime and has the best experience with in house datalinks.
-The performance of a datalink does not depend on being designed exclusively for a single platform. On the contrary, They are for an entire network-centric warfare ecosystem, which should allow adaptation to multiple platforms… this is their essence
-Autonomy or performance goals of KIzılema depends more on mission computers and AI than on the datalink itself as we all clearly know I.e Mission computers, Sensor fusion… Decision making algorithms and library...
-In your argument where you try to imply “a dedicated datalink is mandatory for autonomous wings” is quite weak the real differentiation is in highe level software and autonomy architecture….
-ASELSAN’s architecture (calling ASELSAN ICNAIR-IVDL just a stealth communication would be an injustice, it is a stealth networking ) is not a fixed solution or KAAN only solution and open to Platform specific optimization again a very clear and simple example F 35 and B 21 will use the same directional data link i.e (MADL)
-More importantly
RELAY CAPABILITY stated in ASELSAN ICNAIR-IVDL is
the most clear indication for MUM-T and Collaborative Combat Aircraft concepts..... KAAN is Decision node - sensor fusion - command authority,
KIZILELMA is High performance Forward sensor + shooter + forward relay CCA and
ANKA 3 is Low RCS long endurance CCA.
-KAAN will not only receive and provide data to KIZILELMA & ANKA 3 but also be able to use KIZILELMA & ANKA 3 as a relay/proxy to receive data from non stealth platforms ( F-16, EF, AEW&C (Peace Eagle & Umanned AEWs , surface ships, ground radars........) under ICNAIR-IVDL control, without compromising KAAN’s stealth. We should not confuse Autonomy with Isolation!
-A sperate data link only results in additional crypto and interface layers and Increased operational complexity for instance F 22 (IFDL) and F 35 (MADL).
-A very clear distinction between TB2, TB3, Akıncı and KIZILELMA is only KIZILELMA is considered for MUM-T with KAAN.
-Needless to say, SATCOM ( between distant and non LOS asset and control center) and individual data links (point to point) are control links between
a UAV and a control center (TB2,TB3, AKINCI, ANKA, ANKA S,AKSUNGUR)
....Network data links (AZRA, T-LINK, ASELSAN ICNAIR-IVDL ) are fundamentally different in architecture and purpose.... yet SATCOM can be integrated into a network (Data link 16, Azra, T-link) as well via gateway or relay nodes (for instance an AWACS platform, a ground-based C2 center, a naval platform, or a dedicated relay node) ...... not in direct combat coordination role... but as a supporting layer for instance Common Operational Picture, track data, identification......
-KIZILELMA can employ SATCOM (communality not be required), AZRA/T-LINK (communality required), and ICNAIR-IVDL (communality required) simultaneously in a dynamicly adaptive manner since each link is assigned to clearly differentiated functional roles.
-In the context of MUM-T involving low-observable (LO) platforms, ASELSAN ICNAIR-IVDL constitutes the essential secure, directional, low-observable combat networking backbone with distributed relay capability, while AZRA and T-LINK enable coordination and interoperability between KAAN and non-stealth platforms without compromising KAAN’s low-observable signature. Even with the inclusion of platforms like Hürjet, F-16, and Eurofighter Typhoon into the MUM-T construct, ICNAIR-IVDL will/may remain vital as the dedicated LPI/LPD (low probability of intercept / low probability of detection) network for communications among KIZILELMA platforms and between KIZILELMA and ANKA-3.
