JASA Standards Handbook Version 2.0

30 October 1997


Previous TOC Next


CHAPTER 1.   OVERVIEW

1 Overview
1.1 Introduction
1.1.1 Purpose
1.1.2 Background
1.1.3 Scope
1.1.4 Applicability
1.1.5 Key Considerations in Using the JSH
1.1.6 Basis for the JSH
1.2 Architecture Relationships
1.2.1 Joint Technical Architecture
1.2.2 Unified Cryptologic Architecture
1.3 Document Organization
1.4 Compliance
1.5 Configuration Management


1.  OVERVIEW

     Today's world is one of constant change and technological innovation and revolution. The worlds of computers and communications are no longer separate, but rather provide a virtual worldwide distributed information architecture. While this provides both new opportunities and new challenges, it also necessitates a new approach to airborne SIGINT systems, one which can take advantage of the technologies and can respond rapidly to the changing environment. This requires that former autonomous systems look at migrating to joint, interoperable open systems focusing on "plug and play" for hardware, software and data to stay relevant to the mission.

     To this end, the Joint Airborne SIGINT Architecture (JASA) has been developed to promote interoperability, responsiveness to changing technology, and compatibility with the new technologies and methodologies. This document lays the foundation for the migration of current systems and developments for the Objective 2010 Architecture of interoperable and synergistic SIGINT systems which support rapid reconfiguration and adaptability.

1.1   INTRODUCTION

     The JASA Standards Handbook (JSH) mandates the minimum set of standards and guidelines for all airborne SIGINT systems. The objective of the JSH is to promote Interoperability, Connectivity, and Modernization (ICM) among airborne SIGINT systems and the SIGINT community as well as among modules of JASA compliant subsystems. The JSH is a "forward-looking" document. It guides the acquisition and development of new and emerging airborne SIGINT systems and provides a baseline towards which existing systems will move. It is not a catalog of all information technology standards currently used within airborne SIGINT systems.

     The thrust of the JSH is to go beyond interoperability at the systems level and achieve interoperability of the hardware and software modules. By addressing both software and hardware standards the JSH will provide maximum leverage of new developments, facilitate technology insertion, and allow more rapid reconfiguration and reprogramming to respond to the dynamic signals environment.

     1.1.1  Purpose

     The purpose of the JSH is to:

     1.1.2  Background

     The evolution of national military strategy in response to post cold war era events has resulted in a new vision for the DoD. Joint Vision 2010 is the conceptual template for how America's Armed Forces will channel the vitality and innovation of our people and leverage technological opportunities to achieve higher levels of effectiveness in joint warfighting. This template provides a common direction to our Services in developing their unique capabilities within a joint framework of doctrine and programs as they prepare to meet an uncertain and challenging future.

     This, combined with the economic reality of a shrinking budget, has resulted in the Office of the Secretary of Defense (OSD) direction to establish a Joint Technical Architecture (JTA) that "will become binding on all future DoD Command, Control, Communications, Computers, and Intelligence (C4I) acquisitions" so that "new systems can be born joint and interoperable, and existing systems will have a baseline to move towards to ensure interoperability."

     The JSH is the product of the airborne SIGINT community, including the Army, Navy, Air Force, Defense Intelligence Agency (DIA), OSD, and National Security Agency (NSA). Inputs and comments have been solicited from the contractor community as well as other government entities.

     1.1.3  Scope

     The scope of the JSH includes Front End Processing services, Information Processing services, Human Computer Interface services, Information Transfer services, Security services and physical services for all airborne SIGINT systems, which includes the associated ground surface systems. It includes all hardware, software, networks, storage devices, recording media, backplanes, chassis, circuit cards, and electrical and mechanical interfaces. The JSH also includes data formats for preprocessed and processed data.

     The JSH also includes standards that support the multi-INT fusion efforts currently being developed by the Joint Interoperable Operator Network (JION) for the Distributed Common Ground Station (DCGS). DCGS is a Defense Airborne Reconnaissance Office (DARO) effort to migrate systems to a multi-INT operator ground workstation consisting of IMINT, MASINT and SIGINT segments. JION is the SIGINT segment. JION builds upon the JASA effort to develop common airborne (including ground/surface) SIGINT operator workstations. JION will utilize standards in the JSH.

     The JSH is a living document and will be updated periodically with continued Service/Agency/Industry participation.

     1.1.4  Applicability

     The JSH applies to all airborne SIGINT systems. An airborne SIGINT system is defined as the airborne SIGINT collection and processing elements, operator elements which include both airborne and ground/surface-based operator workstations, and intra-system datalinks. It also includes applicable mechanical, electrical, and software interfaces that support the SIGINT system.

     1.1.5  Key Considerations in Using the JSH

     The JSH shall be used to determine the specific standards to be implemented for new or upgraded airborne SIGINT systems or components; however, there are several key considerations when using the JSH.

     First, mandated standards shall be implemented by systems that have a need for the corresponding services or interfaces. Mandates are indicated by the use of the word "shall."

     Second, legacy standards, needed to interface to existing systems, may be implemented in addition to the mandated standard.

     Third, the use of standards not identified in the JSH must be additive and must not conflict with the JSH or the Joint Technical Architecture (JTA).

     Fourth, Interface Control Documents (ICDs) or Interface Control Specifications (ICSs) will be developed by the appropriate entity.

     1.1.6  Basis for the JSH

     Version 2.0 of the JSH is based on the JASA Standards Handbook Version 1.0, the C4ISR Architecture Framework, the DoD Technical Architecture Framework for Information Management (TAFIM) Version 3.0, the Joint Technical Architecture (JTA) Version 1.0, the Defense Information Infrastructure (DII) Common Operating Environment (COE) Version 3.0 and the DII Shared Data Environment (SHADE) Concept. Figure 1-1 illustrates the roadmap to the JSH. Other emerging architectures related to JASA are discussed below.

     Standards were chosen based on the following criteria:

1.2   ARCHITECTURE RELATIONSHIPS

     The JASA is part of a hierarchy of architectures (See Figure 1-2). The JTA is the overall DoD technical architecture which establishes the foundation for interoperability among all tactical, strategic, and sustaining base systems. The Unified Cryptologic Architecture (UCA) Technical Architecture will become the overall SIGINT architecture (UCA includes Operational, Systems and Technical Architectures) with intent to transform the cryptologic community's systems into a "single interoperable machine."

 

Figure 1-2   JSH Architecture Relationships

     1.2.1   Joint Technical Architecture

     The JTA is the DoD-level technical architecture and is mandated for all C4I applications including JASA. The JTA provides the "building codes" for a seamless flow of information to support the Warfighter. The current JTA focuses on Information Technology (IT), i.e., the processing, transfer, and protection of information. Future versions of the JTA will expand to include electrical (e.g., buses, and circuit cards) and mechanical interfaces (e.g., chassis, racks, and powerplants).

     The Airborne Reconnaissance (AR) Subdomain (formerly the Airborne Reconnaissance Information Technical Architecture (ARITA)) of the JTA covers the manned and unmanned AR systems. The AR reference model was derived from the JASA Functional Reference Model (FRM) and it mandates the JSH for SIGINT related standards.

     The JSH tailors the JTA information processing standards to meet the needs of airborne SIGINT. For example, the JSH expands upon the JTA to address additional real-time information processing standards and guidance. The JSH also extends beyond information technology to include areas and services the JTA does not currently address. These include airborne SIGINT unique standards for Front End Processing (initial data capture) and physical services (size, weight, power, and environmental conditions).

     1.2.2   Unified Cryptologic Architecture

     The UCA is an emerging architecture that will provide a Cryptologic Information Infrastructure (CII) necessary for the interaction of national and tactical SIGINT sensors and the dissemination of SIGINT-derived information. The UCA CII will provide a seamless web of communications networks, computers, software, databases, applications, data, and security services to meet the needs of the SIGINT community. The UCA Technical Architecture (TA) will enable the implementation of the UCA CII. The UCA TA will be the SIGINT extension to the JTA and will focus on information technology.

     The Integrated Tactical SIGINT Architecture (ITSA) is an emerging interim architecture that is focusing on integrating higher levels of connectivity and interoperability into existing tactical systems. The ITSA communications network forms a "tactical SIGINT internet" to provide connectivity among tactical SIGINT sensor nodes, processing nodes, analysis nodes, and tactical intelligence customer nodes. This "virtual network" may allow either data sharing among assets or a complete remoting capability. There is close and continuing cooperation between the JASA and ITSA efforts.

     The JSH identifies the Information Transfer and Information Processing standards to connect to the ITSA "tactical SIGINT internet". JASA goes beyond ITSA in that it includes standards to promote ICM within the subsystem, allowing hardware and software modules to be added, modified, or deleted as required to respond to evolutionary needs and missions.

1.3   DOCUMENT ORGANIZATION

     The JSH consists of eight chapters plus appendices and annexes:

     Chapter One, "Overview".

     Chapter Two, "JASA Reference Models" introduces the major areas and services in the JASA Reference Model (JRM) and introduces an emerging concept "JASA Interface PointS" (JIPS).

     Chapter Three, "Front End Processing," mandates the standards necessary for precision time and navigation data, signal collection, digitization, distribution, and special preprocessing.

     Chapter Four, "Information Processing," mandates the standards necessary for information processing.

     Chapter Five, "Human Computer Interface (HCI)," mandates the style guides necessary to provide a common "look and feel" to the operator.

     Chapter Six, "Information Transfer Services," mandates the information transfer standards and profiles that are essential for interoperability and connectivity.

     Chapter Seven, "Security Services," mandates the standards necessary to minimize the risk associated with sharing and disseminating information.

     Chapter Eight, "Physical Services," mandates the standards necessary to integrate SIGINT sensors in an airborne environment.

     The Appendices include the following:

     The Annexes provide detailed discussions that support the rationale for standards selection and detailed definitions. Annexes are available upon request.

1.4   COMPLIANCE

     The Tactical SIGINT Program Office (TSPO) shall certify standards compliance for all systems being upgraded, migrated, or developed for integration into the JASA. (See Annex 7)

1.5   CONFIGURATION MANAGEMENT

     This document is under the configuration control of the JASA Standards Working Group (JSWG), which meets periodically to review proposed changes.

     Please send all comments to the JSWG Secretariat at 131 National Business Parkway, Suite 110, Annapolis Junction, MD 20701. Proposed changes may also be submitted via e-mail to Secretariat@jswg.org or via our Comments page.


Previous TOC Next