26 April 1997: Add link to Airborne Reconnaissance Information Technical Architecture

10 March 1997
Source: http://www-jta.itsi.disa.mil/jta/implmemo.doc

                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
Source: http://www-jta.itsi.disa.mil/jta/jtacover.html
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 jta-comment@itsi.disa.mil. Industry and non-DoD comments should be submitted through the DISA Center for Standards (CFS) via jta-comment@itsi.disa.mil

Table of Contents

SECTION 1 OVERVIEW

• 1.1 INTRODUCTION
• 1.1.1 Purpose
• 1.1.2 Background
• 1.1.3 Architectures Defined
• 1.1.3.1 Operational Architecture
• 1.1.3.2 Systems Architecture
• 1.1.3.3 Technical Architecture
• 1.1.4 Scope
• 1.1.5 Applicability
• 1.1.6 How to Use the JTA
• 1.1.7 JTA Relationship to DOD Standards Reform
• 1.1.8 Basis for the Joint Technical Architecture
• 1.1.9 JTA Relationships
• 1.2 DOCUMENT ORGANIZATION
• 1.2.1 General
• 1.2.2 Information Processing Standards
• 1.2.3 Information Transfer Standards
• 1.2.4 Information Modeling and Information Standards
• 1.2.5 Human-Computer Interfaces
• 1.2.6 Information Systems Security Standards
• 1.2.7 Appendices
• 1.2.8 Annexes
• 1.2.9 Supplements
• 1.3 CONFIGURATION MANAGEMENT

SECTION 2 INFORMATION PROCESSING STANDARDS

• 2.1 INTRODUCTION
• 2.1.1 Purpose
• 2.1.2 Scope
• 2.1.3 Background
• 2.2 MANDATES
• 2.2.1 Application Software Entity
• 2.2.2 Application Platform Entity
• 2.2.2.1 Service Areas
• 2.2.2.1.1 Software Engineering Services
• 2.2.2.1.2 User Interface Services
• 2.2.2.1.3 Data Management Services
• 2.2.2.1.4 Data Interchange Services
• 2.2.2.1.5 Graphic Services
• 2.2.2.1.6 Communications Services
• 2.2.2.1.7 Operating System Services
• 2.2.2.2 Application Platform Cross-Area Services
• 2.2.2.2.1 Internationalization Services
• 2.2.2.2.2 Security Services
• 2.2.2.2.3 System Management Services
• 2.2.2.2.4 Distributed Computing Services
• 2.3 EMERGING STANDARDS
• 2.3.1 Software Engineering Service
• 2.3.2 User Interface
• 2.3.3 Data Management
• 2.3.4 Data Interchange
• 2.3.5 Operating Systems

SECTION 3 INFORMATION TRANSFER STANDARDS

• 3.1.1 Purpose
• 3.1.2 Scope
• 3.1.3 Background
• 3.2 MANDATES
• 3.2.1 End System Standards
• 3.2.1.1 Host Standards
• 3.2.1.1.1 Application Support Services
• 3.2.1.1.2 Transport Services
• 3.2.1.2 Video Teleconferencing (VTC) Standards
• 3.2.1.3 Facsimile Standards
• 3.2.1.3.1 Analog Facsimile Standard
• 3.2.1.3.2 Digital Facsimile Standards
• 3.2.1.4 Secondary Imagery Dissemination Standards
• 3.2.2 Network Standards
• 3.2.2.1 Router Standards
• 3.2.2.1.1 Internet Protocol (IP)
• 3.2.2.1.2 IP Routing
• 3.2.2.2 Subnetworks
• 3.2.2.2.1 Local Area Network (LAN)
• 3.2.2.2.2 Point to Point Standards
• 3.2.2.2.3 Combat Net Radio Networking
• 3.2.2.2.4 Integrated Services Digital Network (ISDN)
• 3.2.2.2.5 Asynchronous Transfer Mode (ATM)
• 3.2.3 Transmission Media
• 3.2.3.1 Military Satellite Communications (MILSATCOM)
• 3.2.3.1.1 Ultra High Frequency (UHF) Satellite Terminal Standards
• 3.2.3.1.2 Super High Frequency (SHF) Satellite Terminal Standards
• 3.2.3.1.3 Extremely High Frequency (EHF) Satellite Payload and Terminal Standards
• 3.2.3.2 Radio Communications
• 3.2.3.2.1 High Frequency (HF)
• 3.2.3.2.2 Very High Frequency (VHF)
• 3.2.3.2.3 Ultra High Frequency (UHF)
• 3.2.3.2.4 Super High Frequency (SHF)
• 3.2.3.2.5 JTIDS/MIDS Transmission Media
• 3.2.3.3 SONET Transmission Facilities
• 3.3 EMERGING STANDARDS
• 3.3.1 Information Transfer Standards
• 3.3.2 End System Standards
• 3.3.2.1 Internet Standards
• 3.3.2.2 Video Teleconferencing (VTC) Standards
• 3.3.2.3 Global Positioning System (GPS)
• 3.3.3 Network Access Protocols
• 3.3.3.1 Network Access Protocols
• 3.3.3.2 Link 22 Transmission Standards
• 3.3.4 Video Teleconferencing (VTC) Standards
• 3.3.4 Military Satellite Communications (MILSATCOM)

SECTION 4 INFORMATION MODELING AND INFORMATION STANDARDS

• 4.1 INTRODUCTION
• 4.1.1 Purpose
• 4.1.2 Scope
• 4.1.3 Background
• 4.2 MANDATES
• 4.2.1 Activity model
• 4.2.2 Data Model
• 4.2.3 DoD Data Definitions
• 4.2.4 Information Standards
• 4.2.4.1 Information Standards Applicability
• 4.2.4.2 Tactical Information Standards
• 4.2.4.2.1 Bit-Oriented Data
• 4.2.4.2.2 US Message Text Format (USMTF) Messages
• 4.2.4.2.3. Database to Database Exchange
• 4.3 EMERGING STANDARDS
• 4.3.1 Activity model
• 4.3.2 Data Modeling
• 4.3.3 DoD Data Definitions
• 4.3.4 Information Standards

SECTION 5 HUMAN-COMPUTER INTERFACES

• 5.1 INTRODUCTION
• 5.1.1 Purpose
• 5.1.2 Scope
• 5.1.3 Background
• 5.2 MANDATES
• 5.2.1 General
• 5.2.2 Style Guides
• 5.2.2.1 Commercial Style Guides
• 5.2.2.2 DoD HCI Style Guide
• 5.2.2.3 Domain-level Style Guides
• 5.2.2.4 System-level Style Guides
• 5.3 EMERGING STANDARDS

SECTION 6 INFORMATION SYSTEMS SECURITY STANDARDS

• 6.1 INTRODUCTION
• 6.1.1 Purpose
• 6.1.2 Scope
• 6.1.3 Background
• 6.2 MANDATES
• 6.2.1 Introduction
• 6.2.2 Information Processing Security Standards
• 6.2.2.1 Application Software Entity Security Standards
• 6.2.2.2 Application Platform Entity Security Standards
• 6.2.2.2.1 Data Management Services
• 6.2.2.2.2 Operating System Services Security
• 6.2.3 Information Transfer Security Standards
• 6.2.3.1 End System Security Standards
• 6.2.3.1.1 Host Security Standards
• 6.2.3.2 Network Security Standards
• 6.2.3.2.1 Internetworking Security Standards
• 6.2.3.3 Transmission Media Security Standards
• 6.2.4 Information Modeling And Information Security Standards
• 6.2.5 Human-Computer Interface Security Standards
• 6.3 Emerging Standards
• 6.3.1 Introduction
• 6.3.2 Information Processing Security Standards
• 6.3.2.1 Application Software Entity Security Standards
• 6.3.2.1.1 Evaluation Criteria Security Standards
• 6.3.2.1.2 World Wide Web Security Standards
• 6.3.2.2 Application Platform Entity Security Standards
• 6.3.2.2.1 Software Engineering Services Security
• 6.3.2.2.2 Operating System Services Security
• 6.3.2.2.3 Distributed Computing Services Security Standards
• 6.3.3 Information Transfer Security Standards
• 6.3.3.1 End System Security Standards
• 6.3.3.1.1 Host Security Standards
• 6.3.3.2 Network Security Standards
• 6.3.3.2.1 Internetworking Security Standards
• 6.3.4 Information Modeling and Information Security Standards
• 6.3.5 Human-Computer Interface Security Standards

APPENDIX A - ACRONYMS

APPENDIX B LIST OF MANDATED STANDARDS AND SOURCES

• Information Processing Mandated Standards
• Information Transfer Mandated Standards
• Information Modeling and Information Mandated Standards
• Human-Computer Interfaces Mandated Standards
• Information Systems Security Mandated Standards
• DOCUMENT SOURCES
• Commercial Documents
• Government Documents

APPENDIX C - JTA RELATIONSHIP TO DOD STANDARD REFORM

• C.1 DOD (Specifications and) Standards Reform - Background
• C.2 The JTA and the DOD Standards Reform
• C.3 Reform Waiver Policy
• C.4 Non-DoDISS documents not subject to the Reform Waiver Policy
• C.5 Interface Standards are Waiver-Free
• C.6 Non-Government Standards Vs Military/Federal Standardization Documents

USMC SUPPLEMENT

• USMC 1.1 INTRODUCTION
• USMC 1.1.1 Purpose
• USMC 2.1 MANDATES
• USMC 2.1.1 Introduction
• USMC 2.1.2 Information Processing Standards
• USMC 2.1.2.1 Minimum Desktop Computer Configuration and Software Product Requirements
• USMC 2.1.2.2 Marine Corps Software
• USMC 2.1.3 Information Transfer Standards
• USMC 2.1.4 Information Modeling and Information Standards
• USMC 2.1.5 Human Computer Interface
• USMC 2.1.6 Information Systems Security Standards
• USMC 3.1 EMERGING STANDARDS

Frequently Asked Questions (FAQ)

Go to next section.

Return to Table of Contents