From 19 to 30 October 2026, NATO is testing how military digital technologies work together at DiBaX in Latvia. In a report published on 28 October, the NCIA describes tests integrating counter-UAS into C2 and air defence. Data exchange between sensors, effectors and command and control systems is also being examined. NCIA on DiBaX26
A connection does not yet mean shared understanding
ACT’s Next Generation Targeting project is developing a shared data model for targets, intents, tasks and effects. National systems are intended to remain in place. DiBaX26 is intended to test their exchange of information across the tactical, operational and strategic levels. ACT on the data model and experimentation
An interface transmits a report. The receiving system must also understand which object it refers to, when the observation was made and how certain the association is. Two reports about the same missile must not enter the situational picture as two separate objects without verification.
Procurement must test how systems understand data
Technical acceptance testing should cross system boundaries. Are the provenance, timing and uncertainty of an observation preserved during exchange? Can a corrected association be traced in the receiving system?
ACT explicitly states that successful experiments do not demonstrate operational readiness. The decision to use a weapon remains with a human. Faster data processing does not replace that responsibility. Limits of experimentation and human control
Domain models on your own infrastructure
In its ODFF description, Orcrist outlines the connection of distributed sources and an overlying layer that models domain objects and relationships. Orcrist lists private cloud, on-premises and air-gapped deployment as operating options.
This description provides evidence of neither participation in DiBaX nor integration with NATO C2. Supported data models, interfaces and evidence of suitability for the operating environment must be assessed for each specific project.