This is an UNCLASSIFIED extract of the Joint Airborne SIGINT Architecture (JASA) Handbook. The complete version is classified SECRET and can be accessed using Intelink under the DARO Home Page at "http://www.server.daro.ic.gov". For those in government or industry who do not have access to Intelink and desire a complete version of the JASA Handbook, please contact Mr. Dave Camacho, at (301) 483-6000 x2071, or E-Mail email@example.com.
Industry and government are strongly encouraged to provide any comments or questions in writing to Ms. Carolyn Fry, the JSWG chair at (301) 688-0201 (unclassified FAX) or (301) 688-0500 (STU-III FAX), or E-Mail firstname.lastname@example.org.
This document lays a foundation for the migration of current systems and developments to the Objective 2010 Architecture of interoperable and synergistic SIGINT systems as defined by the Joint Chiefs of Staff "Joint Vision 2010". It establishes an open system that will quickly and readily allow for the integration of new capabilities in response to the changing threat environment. The Handbook also identifies standards available and mature enough today to allow upgrades and new developments to start moving towards that objective.
This document is the product of the Airborne SIGINT community, including the Army, Navy, Air Force, Defense Intelligence Agency (DIA), Office of the Secretary of Defense (OSD). Inputs and comments have been solicited from the contractor community as well as government entities.
In general, the JASA Handbook shall be used to determine the specific standards to be implemented within new or upgraded airborne SIGINT systems or components. However, there are several key considerations when using the JASA Handbook.
First, the mandatory standards in the JASA shall be implemented by systems that have a NEED for the corresponding services. That is, if a resource interface is going to be implemented, it shall be implemented in accordance with the associated standard. If a resource is covered by more than one standard, the appropriate standard should be selected based on system requirements. Mandates are indicated by use of the word "shall".
Second, certain standards are recommended rather than mandated. This is particularly true in areas where there is not a clear case for a single standard. In these instances, "acceptable" standards are given, with the "preferred" one identified. If it does not make sense to use the preferred standard, the rationale/justification for using an alternative should be documented. Again, as with mandates, a standard is recommended in the sense that if a resource interface is going to be implemented, it should be implemented in accordance with the associated standard. Recommendations are indicated by use of the word "should".
Third, the JASA Handbook is a "forward-looking" document. It guides the acquisition and development of new and emerging airborne SIGINT functionality and provides a baseline towards which existing systems will move. It is NOT a catalog of all information technology standards used currently within airborne SIGINT systems. It represents those standards (for resource interfaces) that should be used now and in the future. If legacy standards are needed to interface to existing systems, they can be implemented in addition to the standard.
Fourth, any other standards (outside of those identified in the JASA Handbook) must be additive, complementary, and not in conflict with the JASA mandated standards.
Finally, many standards define a generic implementation profile, with tailored specifications needed to provide a single implementation to meet domain or system-specific requirements. In those cases, a commercial standard may be further defined by a standard profile, such as the FIPS Pub 127-2, to ensure proper operation. In some cases, Interface Control Documents (ICDs) will be necessary.
Standards were chosen based on the following criteria: