: How can the Services benefit from a more detailed description of the basis for joint interoperability? Without interoperable systems, we cannot truly have "joint operations." Instead, we have a collection of forces from more than one service -- and possibly even from more than one country -- conducting independent operations in the same geographical area. We cannot work together in a cooperative, coordinated, mutually supportive effort to win on the battlefield if we cannot communicate, and communication is dependent on interoperable systems. The Joint Technical Architecture (JTA) was developed to provide DOD systems with the basis for the seamless interoperability necessary to ensure that we can truly conduct joint operations. This paper describes the three architectural components (views) of the JTA, and then proposes additional detail for one of these three components. Our goal is to help improve interoperability of joint forces by providing a more detailed description of the requirements which must be considered when new systems are being developed. This work is the result of engineering support conducted by the Joint Forces Program Office under the direction of the US Atlantic Command J6.

/pdf/a-basis-for-joint-interoperability-3q8ye1whpn.pdf

A Basis for Joint Interoperability

: The Study was conducted from January to July, 1994. The Study Sponsor was the Director of Information Systems & Command, Control, Communications and Computers. The Study Terms of Reference were tor the ASB to: (1) Define a C3I Technical Architecture; (2)Review and analyze previous Technical Architecture studies; (3) Define a process for development a Technical Architecture; (4) Assist the Army in developing the Technical Architecture; (5) Identify projects where the Technical Architecture can be immediately applied; (6) Suggest organizational and management changes necessary to support the Technical Architecture; and (7) Define how organizational entities should support the transition to the Technical Architecture. The Study Panel recommended that the Army, in the near term (0-1 year): (1) Establish the Technical Architecture components; (2) Designate an Army Technical Architect; (3) Establish an Army Systems Engineering Element to support the Architect; (4) Establish a streamlined management structure; (5) Implement near-term program changes: (6) Encourage Battle Labs and RDECs to use the Technical Architecture for all C3l demonstration programs; and (7) Develop a security policy for the future threat. The Study Panel further recommended that the Army, in the mid-term (1-3 years): (1) Evolve the Technical Architecture as new commercial technologies are introduced; and (2) Establish a single Army/DoD message standard/system.

Michael S. Frankel

Papers

Technical Information Architecture for Army Command, Control, Communications and Intelligence. 1994 Summer Study.