26 April 1997: Add link to Airborne Reconnaissance Information Technical Architecture
10 March 1997
OFFICE OF THE SECRETARY OF DEFENSE WASHINGTON, DC 20301 MEMORANDUM FOR SECRETARIES OF THE MILITARY DEPARTMENTS CHAIRMAN OF THE JOINT CHIEFS UNDER SECRETARIES OF DEFENSE ASSISTANT SECRETARIES OF DEFENSE GENERAL COUNSEL OF THE DEPARTMENT OF DEFEN5E INSPECTOR GENERAL OF THE DEPARTMENT OF DEFENSE DIRECTOR OPERATIONAL TEST AND EVALUATION ASSISTANTS TO THE SECRETARIES OF DEFENSE DIRECTORS OF THE DEFENSE AGENCIES DIRECTOR, JOINT STAFF SUBJECT: Implementation of the DoD Joint Technical Architecture Effective military operations require the ability to respond with a mix of forces, anywhere in the world, on a moment's notice. Interoperability is essential for these joint operations. Information must flow seamlessly and quickly among DoD's sensors, processing and command centers, and shooters, to enable dominant battlefield awareness and operations inside the enemy's decision loop. The DoD Joint Technical Architecture (JTA) is a key piece of DoD's overall strategy to achieve this capability. Its open, standards-based approach also offers significant opportunities for reducing cost and cutting development and fielding time through enhancing software portability, use of COTS, ease of systems upgrade and hardware independence. The JTA is the result of collaboration among the Services, Joint Staff, USD(A&T), ASD(C3I), DISA, DIA, and other elements of the Intelligence Community. The JTA specifies a set of performance-based, primarily commercial, information processing, transfer, content, format and security standards. These standards specify the logical interfaces in command, control and intelligence systems and the communications and computers (C4I) that directly support them. The JTA is a practical document, identifying standards where products are available today. It is entirely consistent with and supportive of DoD's Specification and Standards Reform. Effective immediately, the JTA (Version 1.0) is mandatory for all emerging systems and systems upgrades. The JTA applies to all C4I systems and the interfaces of other key assets (e.g., weapons systems, sensors, office automation systems, etc.) with C4I , systems. The JTA also applies to C4I Advanced Concept Technology Demonstrations and other activities that lead directly to the fielding of operational C4I capabilities. The Services, Agencies and other Components are responsible for the implementation of the JTA (including enforcement, budgeting and determining the pace of systems upgrades). All emerging C4I systems and C4I systems upgrades are to comply with the JTA. Existing C4I systems are to migrate to the applicable JTA standards, while considering cost, schedule and performance impacts. waivers may be granted only by Service, Agency and other Component Acquisition Executives, with the concurrence of the ASD(C3I) and the USD(A&T). In this context, non- response after two weeks from the date of receipt by OSD constitutes concurrence. Each Service, DoD Agency, and applicable other Component is requested to provide a plan outlining its approach to implementing the JTA to ASD(C3I) and USD(A&T) within 90 days. The JTA is a living document that will evolve as technology and the marketplace change. Within 90 days, the USD(A&T) and ASD(C3I), with the support of the Services and Agencies, will develop a proposal for updating, maintaining, and configuration managing the JTA. It is our intention to expand the scope of the JTA to encompass all systems with which the C4I systems will directly interact. implementation experiences will be fed back into the JTA to ensure that it is the best technical guidance for our developers. The goal of the JTA is interoperability and effectiveness in a joint and ultimately a coalition environment; tests and exercises will be used to evaluate progress. For applicable systems, the JTA replaces the standards guidance in the Technical Architecture Framework for Information Management (TAFIM) currently cited in DoD Regulation 5000.2-R. Request Director, Joint Staff forward this memorandum to the Unified Combatant Commands. AUG 22 1996 /Signed/ /Signed/ Paul G. Kaminski Emmett Paige, Under Secretary of Defense Assistant Secretary (Acquisition and Technology) (Command, Control, Communications and Intelligence)
10 March 1997
Note: Hyperlinks below are to JTA site.
The Warfighter battlespace is complex and dynamic, requiring timely and clear decisions by all levels of military command. Warfighters must be able to work together within and across Services in ways not totally defined in today's operational concepts and/or architectures. There is an unprecedented increase in the amount of data and information necessary to conduct operational planning and combat decision making. Warfighters must be able to obtain and use intelligence from theater and National assets which may be processed in forward areas or Continental United States (CONUS). Today's split base/reach back concept requires them to obtain their logistics and administrative support from both home bases and deployed locations. All of this requires that information quickly and seamlessly flow among DoD's sensors, processing and command centers and shooters to achieve dominant battlefield awareness and move inside the enemy's decision loop.
The Joint Technical Architecture (JTA) provides the "building codes" which, when implemented, permit this flow of information in support of the Warfighter. The JTA identifies a common set of mandatory information technology standards and guidelines to be used in all new and upgraded C4I acquisitions across DoD. The JTA standards are to be used for sending and receiving information (information transfer standards such as Internet Protocol suite), for understanding the information (information content and format standards such as data elements, or image interpretation standards) and for processing that information. The JTA also includes a common human-computer interface and "rules" for protecting the information (i.e., information system security standards).
The scope of this initial version of the JTA is focused on Command, Control and Intelligence systems (to include sustaining base, combat support information systems, and office automation systems) and the Communications and Computers that directly support them (C4I), and the interfaces of those systems with other key assets (e.g., weapon systems, sensors, models and simulations) to support critical joint Warfighter interoperability. Future versions of the JTA will extend the Version 1.0 scope from C4I Systems to include these other domains.
The JTA draws on the Technical Architecture Framework for Information Management (TAFIM), which provides general guidance and documents the processes and framework for defining the JTA and other technical architectures. The TAFIM applies to many DoD mission/domain areas and lists all adopted information technology standards that promote interoperability, portability, and scalability. The JTA necessarily includes requirements as related to interoperability by identifying the minimum set of standards. As the JTA evolves, the nature and relationship to the standards information in the TAFIM (particularly Volume 7) will evolve.
The standards and specifications identified in the JTA are entirely consistent with and support the DoD Standards and Acquisition Reform initiatives. The DoD standards policy recognizes the need for DoD to specify interface standards that are required for interoperability. The standards in the JTA are almost entirely performance-based interface standards. Most are commercial standards. None of the military standards require a waiver to use.
The JTA will be used by anyone involved in the management, development, or acquisition of new or improved C4I systems within DoD. Specific guidance for implementing this JTA is provided separately. While the strategy for implementation is being formulated and discussed now, the guiding principle generally agreed to is that the responsibility for specific implementation details, enforcement decisions and mechanisms will be determined by each of the Services and Agencies Acquisition Executives (SAEs). System developers will use the JTA to ensure that new and upgraded C4I systems (and the interfaces to such systems) meet interoperability requirements. System integrators will use it to facilitate the integration of existing and new systems. Operational requirements developers will be cognizant of the JTA in developing requirements and functional descriptions. When developing C4I applications for Advanced Technology Demonstrations (ATDs), the science and technology community will use the JTA whenever possible to provide the logical interfaces to existing C4I, so that their good ideas will readily integrate into existing systems rather than require a massive redesign to meet DoD's interoperability objectives. The JTA is applicable to Advanced Concept Technology Demonstrations (ACTDs).
The JTA is a forward looking document, defining the standards to which we want to build new and upgraded systems. The intent is to clearly indicate migration direction. Legacy standards such as TADIL A, B, and C are not included. Existing systems are not expected to immediately conform to the JTA. When these systems are upgraded, the JTA will be used to transition the system towards a common interoperability goal. If legacy standards are needed to interface to existing systems they can be implemented with appropriate approval in addition to the mandated standard. Ultimately the SAEs will determine whether systems conform to the JTA, when and to what degree, based upon the business case for each acquisition.
The JTA must be a "living" document. The JTA must evolve with time as technology and the marketplace changes. In addition, it is intended that the scope of the JTA will expand to include other domains. The JTA will be jointly configuration managed by the CINCs, Services and Agencies (C/S/As). Proposed changes should be provided to the JTA point of contact identified by your CINC/Service/Agency. Changes may also be submitted via email@example.com. Industry and non-DoD comments should be submitted through the DISA Center for Standards (CFS) via firstname.lastname@example.org
Go to next section.
Return to Table of Contents