Somebody has to turn this into a sentence in a tender document, and that sentence is where a demonstration either holds up or quietly evaporates.
Draw the grid first. One axis is whose network carried the track: a vendor test harness, or the network the unit actually fights on. The other axis is what the track was permitted to do on arrival, meaning paint a symbol on a display versus feed the assignment that points a weapon. Manching sits on the right side of the first axis, because the fusion happened inside NATO's Link 16 [5]. Where it sits on the second is less clear. The picture was integrated into Skymaster [2], and Skymaster was the system directing the Skynex battery in the scenario [3], but the release never says a Twinvis-derived track on its own was the basis for an engagement [14]. Skymaster is also built to fuse active radar and electro-optical inputs [8], so a passive contribution to a picture and a passive track you would shoot on are not the same purchase.
The release carries no numbers either. No detection range, no track count, no accuracy figure, no fusion latency, and no calendar date beyond the exercise name [13]. What survives is a qualitative statement from the two companies that the passive radar performed well at detecting and tracking air targets [6], which is a sentence that reads identically whether the tracks were solid or merely present.
Then there is the tense. The findings are described as an excellent foundation for integration into stationary Skynex systems, mobile Skyranger solutions and counter-UAS products such as Skyspotter [11]. One of those, Skynex, had a battery in the scenario being directed by the very system that took the Twinvis feed [15]. The honest reading is that an interface worked once, under exercise conditions, in a configuration nobody can yet order off a price list.
The reason a buyer wants it anyway is emissions control. Rheinmetall and Hensoldt pitch the combination as resilient, low-emission surveillance in line with an EMCON strategy, aimed at protecting high-value infrastructure, critical facilities and mobile units [9], and they rest the survivability argument on the absence of a distinctive identification to detect [10]. That argument only converts into money if the passive track is trusted far enough down the chain that the active radars can stay quiet.
Which points at how to write the requirement: as a behaviour rather than a component. The C2 system shall accept, correlate and permit weapon assignment on third-party passive tracks over Link 16, at a stated track quality. The cost of that phrasing is that acceptance testing becomes an argument about thresholds rather than a checkbox, and the supplier pair that just ran the demonstration will want to set those thresholds. The alternative, naming Twinvis and Skymaster in the specification, buys a clean test and ties the whole air picture to one pair of vendors [2].
