HAVELSAN ADVENT: Turkey’s First Indigenous Naval Combat Management System, Explained

Image: TCG Burgazada (F-513), an Ada-class corvette running HAVELSAN ADVENT — U.S. Navy photo by MC3 Louis Staats, public domain (Wikimedia Commons).
Step onto the bridge of a modern warship and the picture is overwhelming: dozens of screens, hundreds of radar tracks, a sonar feed humming below, helicopter radios crackling, allied aircraft pouring data over a tactical link, command orders flashing in by the second. The piece of software that takes all of that noise, fuses it into a single sea picture, and tells the captain which target to shoot, with which weapon, right now is the ship’s combat management system — and on Turkish warships, that software is HAVELSAN’s ADVENT.
ADVENT — short for Ağ Destekli Veri Entegre Savaş Yönetim Sistemi, “Network-Enabled Data Integrated Combat Management System” — is the first combat management system Turkey has ever designed and written end-to-end at home. Today it runs on platforms from the Ada-class corvettes and the country’s largest warship TCG Anadolu, to corvettes exported to Pakistan and Ukraine. It is, in plain terms, the brain of the Turkish fleet.
The story starts in 2010. Until then, every new Turkish warship had to buy its combat management system from a foreign supplier — meaning every software update needed permission, every weapon integration needed a negotiation, and every export deal needed a third-country sign-off. HAVELSAN launched ADVENT with a clear brief: build one open-architecture software backbone that could be installed on anything from a patrol boat to an amphibious assault ship, talk fluently to NATO partners, and carry only Turkish source code.
At a Glance
What a Ship’s Brain Actually Does
Every sensor bolted onto a modern warship — the surface-search radar, the air-search radar, the sonar listening through the hull, the electronic-warfare receivers, the optical cameras, the IFF transponder that asks “friend or foe?”, the helicopter circling overhead, even the data link feed from an allied aircraft a hundred miles away — produces thousands of data points a second. ADVENT does not show those one by one. It fuses them into a single picture of the sea and prints that picture on the operator’s screen.
If the same enemy ship is being painted by both the radar and the optical camera, ADVENT recognises it as one contact, not two — work that used to require two separate operators staring at two separate screens. The real payoff is at the speed of decision: the commander on the bridge asks “what is that, who can shoot it, and with what?” by pointing and clicking. ADVENT pushes the firing solution down to the gun, the missile launcher, the torpedo tube, or the electronic-warfare jammers. The engagement chain closes in less time than a human takes to think it through.
Mission Profiles
Specifications
| Specification | Value |
|---|---|
| Type | Network-enabled, distributed-architecture combat management system |
| Developer | HAVELSAN (software lead), with ASELSAN on sensor integration |
| Data Links | Link 11, Link 16, Link 22, JREAP-C, SIMPLE, VMF |
| Standards | NATO-compatible message formats (ADatP-3, MIL-STD-6016) |
| Mission Modules | Surface, air, sub-surface, electronic warfare, asymmetric threat, amphibious support |
| Architecture | Open, modular — new sensors or weapons plug in without rewriting the whole stack |
| First Deployment | TCG Heybeliada (F-511), 2011 |
Which Ships Run It
The interesting thing about ADVENT is that it is not “one ship’s software.” It is a software family — the same core is recompiled and tailored ship by ship.
- MILGEM Ada-class corvettes — TCG Heybeliada, Büyükada, Burgazada, Kınalıada. ADVENT’s first operational home, and the platform where most of its early testing happened.
- Pakistan Navy Babur-class corvettes — Turkey’s first warship export, and the first overseas deployment of ADVENT.
- Ukrainian Navy Hetman Ivan Mazepa — an Ada-class corvette built for the Black Sea, with ADVENT exported as part of the package.
- TCG Anadolu (LHD) — Turkey’s amphibious assault ship runs a tailored “LHD SYS” variant that also helps marshal the air wing on deck.
- DİMDEG (TCG Alemdar) — a sub-surface variant focused on submarine-rescue operations.
- Offshore Patrol Vessels (OPV) — the Turkish Navy’s new patrol vessel programme integrates ADVENT as standard.
- İstif-class frigates — TCG Istanbul, the lead ship of the I-class, runs an ADVENT derivative.
- MELTEM-2 CN-235 maritime patrol aircraft — yes, an aircraft. An airborne ADVENT version shares the same sea picture with the surface fleet.
Why It Matters for Turkey
A combat management system is the most critical piece of software on a warship. If the source code belongs to someone else, the ship — at least operationally — belongs to someone else too. Before ADVENT, every new ship Turkey bought meant another foreign licence negotiation, with both cost and political risk attached: the supplier country could, in principle, slow-roll an upgrade, refuse an export sign-off, or veto a third-country sale.
With ADVENT, Turkey joined the small club of countries that not only build their own warships but also write the software that runs them — and can sell both together as a single package. That is exactly why Pakistan and Ukraine bought it. They did not pick ADVENT because it is “the Turkish standard”; they picked it because no third country needed to approve the deal. The NATO-compatible message set, meanwhile, keeps Turkish ships interoperable with allied fleets on the same operation.
Summary
| What does it do? | Fuses every sensor, weapon and radio on a warship into one decision picture. |
|---|---|
| Why is it important? | Turkey’s first home-built combat management system — no foreign export-licence chokepoint. |
| Where is it deployed? | MILGEM corvettes, TCG Anadolu, İstif-class frigates, and exports to Pakistan and Ukraine. |
| What it means for Turkey | Software sovereignty for the navy plus an exportable warship-plus-software package. |
Sources:

