Making available assets work together
Cobalt’s intended commando users operate across large distances in the north. Those units depend on the sensors and uncrewed systems they carry. That is the coordination problem behind the Cobalt contract: making the available equipment work within the same mission. The military relevance of the multimillion-pound software purchase lies in its intended service to this dispersed force.[1]
Cobalt is intended to combine sensors, autonomous platforms and data feeds in one interface. The stated functions include oversight of several assets, updates to personnel teams and use of gathered information. My assessment is that the first potential gain concerns the burden of coordination before the number of additional platforms. A narrower explanation is possible: the software may chiefly organise existing information, with limited benefit to how quickly units work in the field.[1]
Shared mission, joint testing
Planned joint testing with Norwegian units brings the allied dimension of the purchase into view. Arondite announced 35 million pounds of investment in Norway over five years. Cobalt is to be made available for joint testing during forthcoming deployments. Britain’s commando structure already brings marines together with artillery, aviation, communications and logistics elements. In that force, the value of one interface concerns its contribution to different elements sustaining the same mission.[1]
The joint-test plan does not provide a completed field result. Announcing the contract does not measure combat effect either. My judgement of Cobalt is therefore bounded: it is a procurement choice aimed at managing the assets of a dispersed force. Enabling marines to use the equipment available to them together is the military requirement at its centre.[1]