considered by the architectures (though not necessarily to those that are immediately adjacent to any given program), and limit the scope of the interoperability effort to particular configurations of components. In other words, interoperability cannot be realistically expected across an unlimited number of releases or versions. Such "bottom-up" negotiation of interoperability issues is intended to complement "top-down" architectural and common infrastructure efforts. The cell would also be responsible for elements that constitute an investment in future interoperability, such as metadata and appropriate interfaces.

The appropriate placement for an interoperability activity can vary. For a large program, placement within the program manager's office may be advantageous. In other cases, placement within a program executive office or service acquisition command may make sense—both for reasons of efficiency and to ensure that the "cell" has a sufficiently broad perspective. Somewhat similar functions have been performed by service elements such as the Air Force Electronic Systems Command, the Navy Space and Naval Warfare Systems Command, and the Army Communications and Electronics Command. However, there is no clear analogy to these organizations for joint systems.



The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement