E2. ENCLOSURE 2

DEFINITIONS

E2.1.1. Architectures. The structure of components, their relationships, and the principles and guidelines governing their design and evolution over time.

E2.1.2. Defense Agencies. All agencies and offices of the Department of Defense including the Ballistic Missile Defense Organization, Defense Advanced Research Projects Agency, Defense Commissary Agency, Defense Contract Audit Agency, Defense Finance and Accounting Service, Defense Information Systems Agency, Defense Intelligence Agency, Defense Legal Services Agency, Defense Logistics Agency, Defense Threat Reduction Agency, Defense Security Cooperation Agency, Defense Security Service, National Imagery and Mapping Agency, National Reconnaissance Office, and National Security Agency.

E2.1.3. Family-of-Systems (FoS). A set or arrangement of independent systems that can be interconnected or related in various ways to provide different capabilities. The mix of systems can be tailored to provide desired capabilities dependent on the situation or mission.

E2.1.4. Information Assurance (IA). Information operations that protect and defend information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation. This includes providing for restoration of information systems by incorporating protection, detection, and reaction capabilities.

E2.1.5. Information Exchange Requirements (IERs). The requirement for information to be passed between and among forces, organizations, or administrative structures concerning ongoing activities. Information exchange requirements identify who exchanges what information with whom, as well as, why the information is necessary and how that information shall be used.

E2.1.6. Information Superiority. The capability to collect, process, and disseminate an uninterrupted flow of information while exploiting or denying an adversary's ability to do the same.

E2.1.7. Information Technology (IT). Any equipment, or interconnected system or subsystem of equipment, that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information by the executive agency. This includes equipment used by a Component directly, or used by a contractor under a contract with the Component, which (i) requires the use of such equipment, or (ii) requires the use, to a significant extent, of such equipment in the performance of a service or the furnishing of a product. The term "IT" also includes computers, ancillary equipment, software, firmware and similar procedures, services (including support services), and related resources. Notwithstanding the above, the term "IT" does not include any equipment that is acquired by a Federal contractor incidental to a Federal contract. The term "IT" includes National Security Systems (NSS).

E2.1.8. Information Technology Architecture (ITA). An integrated framework for evolving or maintaining existing information technology and acquiring new information technology to achieve the Agency's strategic goals and information resources management goals.

E2.1.9. Integrated Architecture. An architecture consisting of multiple views or perspectives (operational view, systems view, and technical view) that facilitates integration and promotes interoperability across Family-of-Systems/System-of-Systems and compatibility among related mission area architectures.

E2.1.9.1. The operational architecture view is a description of the tasks and activities, operational elements, and information flows required to accomplish or support a warfighting function.

E2.1.9.2. The systems architecture view is a description, including graphics, of systems and interconnections providing for, or supporting, warfighting functions.

E2.1.9.3. The technical architecture view is the minimal set of rules governing the arrangement, interaction, and interdependence of system parts or elements, whose purpose is to ensure that a conformant system satisfies a specified set of requirements.

E2.1.10. Interoperability. Interoperability is the ability of systems, units or forces to provide data, information, materiel, and services to and accept the same from other systems, units, or forces and to use the data, information, materiel, and services so exchanged to enable them to operate effectively together. IT and NSS interoperability includes both the technical exchange of information and the end-to-end operational effectiveness of that exchange of information as required for mission accomplishment.

E2.1.11. Joint Mission Areas (JMAs). JMAs represent a functional group of joint tasks and activities that share a common purpose, and facilitate joint-force operation and interoperability. JMAs provide a logical way to organize the Joint Operational Architecture. JMAs provide the context for defining FoS/SoS relationships sharing a common mission area.

E2.1.12. Joint Operational Architecture (JOA). Description of tasks and activities, operational elements, and information flows required to accomplish or support military operations; defines types of information exchanged, frequency of exchange, which tasks and activities are supported by information exchanges, and nature of information exchanges in detail sufficient to ascertain specific interoperability requirements.

E2.1.13. Joint Systems Architecture (JSA). The identification and description of all DoD systems and their interconnections necessary to accomplish the tasks and activities described in the Joint Operational Architecture.

E2.1.14. Joint Technical Architecture (JTA). The JTA provides the minimal set of rules governing the arrangement, interaction, and interdependence of system parts or elements, whose purpose is to ensure that a conformant system satisfies a specified set of requirements. The JTA defines the service areas, interfaces, and standards (JTA elements) applicable to all DoD systems, and its adoption is mandated for the management, development, and acquisition of new or modified fielded IT and NSS systems throughout the Department of Defense.

E2.1.15. Key Performance Parameters (KPPs). Those capabilities or characteristics considered most essential for successful mission accomplishment. Failure to meet a KPP threshold can be cause for the concept or system selection to be reevaluated or the program to be reassessed or terminated. Failure to meet a Capstone Requirements Document KPP threshold can be the cause for the FoS/SoS concept to be reassessed or the contributions of the individual systems to be reassessed.

E2.1.16. Materiel Solution. Correction of a deficiency, satisfaction of a need, or incorporation of new technology that results in the development, acquisition, procurement or fielding of a new item (including ships, tanks, self-propelled weapons, aircraft, etc., and related software, spares, repair parts and support equipment, but excluding real property, installations, and utilities) necessary to equip, operate, maintain, and support military activities without disruption as to its application for administrative or combat purposes.

E2.1.17. Mission Area Integrated Architectures. Mission area integrated architectures are the common foundation for mission area focused, outcome-based IT and NSS interoperability and supportability processes. Mission area integrated architectures (consisting of operational, systems, and technical views) are derived from JMAs (i.e., subordinate/supporting missions to the JMAs) and/or business/administrative mission areas. Mission area integrated architectures can cover organizational entities (e.g., Joint Task Force, Navy Battle Group or Army Brigade). The Joint Operational Architecture (JOA), the Joint Systems Architecture (JSA) and the Joint Technical Architecture (JTA) serve as the basis for developing mission area integrated architectures.

E2.1.18. Mission Critical Information Systems (MCIS). A system that meets the definitions of "information system" and "national security system" in the Clinger-Cohen Act (reference (b) ), the loss of which would cause the stoppage of warfighter operations or direct mission support of warfighter operations. (The designation of mission critical should be made by a Component Head, a CINC or their designee.) A Mission Critical Information Technology System has the same meaning as a Mission Critical Information System.

E2.1.19. Mission Essential Information Systems (MEIS). A system that meets the definition of "information system" in the Clinger-Cohen Act (reference (b) ), that the acquiring Component Head or designee determines is basic and necessary for the accomplishment of the organizational mission. (The designation of mission essential should be made by a Component Head, a CINC or their designee.)

E2.1.20. Non-Materiel Solution. Changes in doctrine, organization, training, leadership, personnel or facilities that satisfy identified mission needs.

E2.1.21. National Security System (NSS). Any telecommunications or information system operated by the United States Government, the function, operation, or use of which:

E2.1.21.1. Involves intelligence activities.

E2.1.21.2. Involves cryptologic activities related to national security.

E2.1.21.3. Involves command and control of military forces.

E2.1.21.4. Involves equipment that is an integral part of a weapon or weapons system.

E2.1.21.5. Is critical to the direct fulfillment of military or intelligence missions. This does not include automatic data processing equipment or services to be used for routine administrative and business applications (including payroll, finance logistics and personnel management applications).

E2.1.22. Operational Concept. An end-to-end stream of activities that defines how force elements, systems, organizations, and tactics combine to accomplish a military task.

E2.1.23. Outcome-Based Interoperability. An interoperability process that:

E2.1.23.1. Includes experts from the operational community to identify, consolidate and prioritize interoperability deficiencies; and synchronize non-materiel solutions with materiel solutions for both new and fielded capabilities.

E2.1.23.2. Characterizes IT and NSS interoperability requirements in a family-of-systems or system-of-systems mission area context and relates IT and NSS through integrated architectures derived from the Joint Operational Architecture and associated Joint Mission Areas.

E2.1.23.3. Precisely defines operational user requirements to include interoperability as a Key Performance Parameter.

E2.1.23.4. Incorporates both materiel (acquisition or procurement) and non-materiel (doctrine, organizational, training, leadership, personnel, or facilities) solutions.

E2.1.23.5. Verifies solution sets in formal tests or operational exercises.

E2.1.23.6. Continuously evaluates interoperability Key Performance Parameters and verifies overall IT and NSS interoperability throughout a system's life.

E2.1.24. Supportability. The ability of systems and infrastructure components, external to a specific IT or NSS, to aid, protect, complement, or sustain design, development, testing, training, or operations of the IT or NSS to its required capability.

E2.1.25. System-of-Systems (SoS). A set or arrangement of systems that are related or connected to provide a given capability. The loss of any part of the system will degrade the performance or capabilities of the whole.

E2.1.26. Universal Reference Resources (URRs). Reference models and information standards, which serve as sources for guidelines and attributes that must be consulted while building integrated architecture products. The following are the currently listed URRs: DoD Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) Architecture Framework; C4ISR Core Architecture Data Model; Defense Data Dictionary, Levels of Information Systems Interoperability; Universal Joint Task List; Joint Operational Architecture; Technical Reference Model; Defense Information Infrastructure Common Operating Environment; Shared Data Environment; and the DoD Joint Technical Architecture.