"This paper examines how Russia is transforming its command and control (C2) architecture under wartime pressure, how these changes shape the country’s incremental move toward battlefield-required software solutions, and what lessons U.S. policymakers can learn from Russia’s experiences. Focusing on both strategic ambitions and battlefield practice, the takeaways below summarize how automated C2 systems, unmanned platform management software, and emerging AI applications are being developed, adapted, and scaled within Russia’s military ecosystem.
1. Russia is no longer prioritizing the construction of a single, comprehensive automated C2 architecture comparable to Western joint concepts; instead, it is reallocating effort toward tactical, task-specific software, driven by battlefield necessity. Prolonged, high-intensity combat in Ukraine exposed the limits of centralized, system-wide C2 modernization and elevated the importance of accelerating the tactical kill chain. The emergence of systems such as the “Svod” Tactical Situational Awareness Complex and other integrated reconnaissance-strike tools reflects a pragmatic shift in which operational control of unmanned systems and real-time battlefield management now deliver greater military value than achieving end-to-end C2 integration.
2. Because unmanned systems now conduct up to 80 percent of Russian fire missions, the center of gravity in C2 innovation has shifted toward software that manages drones and integrates them with artillery and other fire units. Civilian engineers and volunteer developers have focused on closing this gap by building tools that provide situational awareness, automate fire correction, and link unmanned aircraft systems (UAS) operators directly to firing units. Russia’s “Glaz/Groza” software complex demonstrates this trend, functioning as a unified reconnaissance-strike workflow that converts drone footage into targeting data and compresses the time from detection to impact from hours to minutes.
3. The Russian military assesses its AI capabilities for visual and audio data processing as relatively mature, placing computer vision, sensor fusion, and signal analysis at technology readiness level (TRL) 6–9, while natural-language processing remains at an early, experimental stage, TRL 1–3. This disparity reflects a deliberate prioritization of AI applications that deliver immediate battlefield utility—such as target recognition, guidance, and autonomous terminal functions for unmanned systems—and where abundant data and combat validation are available. By contrast, text analysis AI, which underpins document processing and higher-level C2 decision support, remains constrained by immature architectures, limited certified software, and organizational barriers, slowing progress toward fully AI-enabled command workflows.
4. Within Russian C2 systems, AI is primarily envisioned as a support function rather than a replacement for human decisionmaking. Russian military doctrine assigns AI two core roles: enhancing the processing and interpretation of sensor data and providing predictive decision support through forecasting, scenario generation, and recommendations for commanders. Across strategic and tactical levels, AI is intended to augment situational awareness and analytical capacity, while formal authority and responsibility for decisions remain firmly with human commanders.
5. Russia began its C2 digitalization effort by building a dense layer of standards governing terminology, system architecture, hardware-software integration, and information management. This standardization drive, coupled with the transition to the domestically controlled Astra Linux operating system, reflects an attempt to create a unified technical foundation capable of supporting data integration, interoperability, and future AI insertion across the command hierarchy. While this framework provides structural coherence, it has not, on its own, resolved deeper institutional and methodological constraints that continue to limit system-wide C2 integration.
6. To enable AI-driven tactical software, the Russian military launched a systematic data collection effort in 2025 focused on unmanned operations and strike outcomes. The emerging data infrastructure aggregates UAS video feeds, operator telemetry, strike effects, and individual pilot performance metrics, each linked to unique personal identifiers. These datasets serve multiple functions simultaneously: operational analysis, training evaluation, and the creation of labeled data for AI model development, establishing a feedback loop that ties battlefield performance directly to software refinement.
7. Despite efforts to reduce dependence on foreign commercial technologies, Russia’s military AI development remains heavily reliant on open-weight models and civilian software ecosystems. The transition from tools such as AlpineQuest and Discord toward domestic alternatives like ZOV Maps and Astra-based platforms reflects a push for security and sovereignty at the application layer. At the same time, Russian developers actively adapt open-weight and commercially available AI models, including Mistral, Qwen, LLaMA, YOLO, and related architectures, for military use, embedding them into on-premise, tightly controlled environments. This hybrid approach allows Russia to mitigate sanctions and accelerate AI adoption without building foundational models from scratch." (Executive summary)