Coalition interoperability has received a good deal of focus during the past few years. The Afghan Mission Network (AMN) has given many hope that a repeatable solution for coalition operations could be developed that would allow rapid deployment of a coalition-compatible network for future conflicts. The Future Mission Network (FMN) is envisioned to allow coalition partners to plug into a standards-compliant network with the functionality and security needed to support complex operations.
Recently, in discussions on the U.S. Defense Department initiative to develop a common operating environment referred to as the Joint Information Environment, or JIE, I began to consider whether the creation of such a common environment for the department would help move toward agile and effective coalition information sharing, or would put more distance between the U.S. military and its partners.
The conclusion I have reached is that the JIE could help or hinder coalition efforts, depending on how the JIE architecture is coordinated and whether it is kept on a path parallel to the FMN. It is important to remember that coalition information sharing today is more than just how the United States works with its foreign allies. Anywhere on the mission spectrum, the Defense Department must work with a wide range of U.S. federal agencies, industry partners and, sometimes, state, local and tribal agencies, as well as with international partners.
This means the legacy architectures, direction and needs of this extremely diverse set of players must be considered at every step of the development of the JIE. And, it is imperative to keep the development of the JIE and the development of the FMN coordinated every step of the way. Failure to do this will make it more difficult, not easier, to work with interagency partners and coalition partners.