Targeted Interoperability

📖 The Scoop

Significant literature exists on all types of interoperability, with the common refrain being that more and better interoperability is needed. And, with few exceptions in recent decades, the United States tends to engage with multinational partners and allies in military operations, thus bringing multinational interoperability to the fore. So, with all this interest, why is the United States not interoperable when and how it wants? There are several reasons, including a lack of understanding of the significant resources that interoperability takes, a reluctance to expend time and money when the value of doing so is not clear, and a one-size-fits-all attitude toward finding solutions. This report looks at what motivations exist for building interoperability and defines a reasonable framework from which to work if and when interoperability needs and investments meet strategic language. The framework proposed has three main parts. First, the authors catalogued nearly 200 programs into ten categories, which comprise "activities" that in one way or another increase interoperability between the United States and its partners. Those activities help to build five main interoperability "outputs": having common equipment, sharing the art of command, having individual interoperability, having interoperable communication and information systems equipment, and having interoperable processes. The "outcomes" are what those outputs lead to. Those are predicated on having specific abilities to share services between at least two partners. The framework necessarily stops short of broader operational outcomes-like winning a war or deterring conflict-as the basic interactions that translate interoperability into qualitative goals of legitimacy or deterrence are not known.

Genre: Computers / Networking / General (fancy, right?)