E2.1.30. 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.
Milestones. Major decision points that separate the phases of an
Decision Authority (MDA). The individual designated according to criteria
established by the USD(AT&L) or by the ASD(C3I) for IT and NSS acquisition
programs to approve entry of an acquisition program into the next phase.
E2.1.33. Military Department. A DoD
Component headed by a civilian Secretary that the President appoints,
including a Military Service (e.g., the Department of the Navy includes two
E2.1.34. 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.35. Mission Critical Information System
(MCIS). A system that meets the definitions of "information system"
and "national security system" in the Clinger-Cohen Act (reference (c)), 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.36. Mission Essential Information System
(MEIS). A system that meets the definition of "information system"
in the Clinger-Cohen Act (reference (c)), that
the acquiring Component Head or designee determines is basic and necessary for
the accomplishment of the organizational mission. (The designation of mission
critical should be made by a Component Head, a CINC or their designee.)
Mission Need. A deficiency in current capabilities or an
opportunity to provide new capabilities (or enhance fielded capabilities)
through the use of new technologies. Mission needs are expressed in broad
operational terms by the DoD Components.
E2.1.38. Mission Need Statement (MNS). A
formatted non-system-specific statement, written in broad operational terms,
that describes operational capability needs, required operational
capabilities, and constraints to be studied during the Concept Exploration and
E2.1.39. National Security System (NSS). Any
telecommunications or information system operated by the United States
Government, the function, operation, or use of which:
E22.214.171.124. Involves intelligence activities.
E126.96.36.199. Involves cryptologic activities related to
E188.8.131.52. Involves command and control of military
equipment that is an integral part of a weapon or weapons
E184.108.40.206. 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
Non-Materiel Solution. Changes in doctrine, organization,
training, leadership, personnel or facilities that satisfies identified
Operational Concept. An end-to-end stream of activities that
defines how force elements, systems, organizations, and tactics combine to
accomplish a military task.
Operational Requirements. A system capability or characteristic
required to accomplish approved mission needs. Operational (including
supportability) requirements are typically performance parameters, but they
may also be derived from cost and schedule. For each parameter, an objective
and threshold value must also be established.
E2.1.43. Operational Requirements Document
(ORD). A formatted statement containing performance and related
operational parameters for the proposed concept or system. Prepared by the
user or users representative at each milestone beginning with Milestone A.
E2.1.44. Outcome-Based Interoperability . An
interoperability process that:
E220.127.116.11. Includes experts from the operational
community to identify, consolidate, and prioritize mission needs and
interoperability deficiencies; and synchronize non-materiel solutions with
materiel solutions for both new and fielded capabilities.
E18.104.22.168. 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.
E22.214.171.124. Precisely defines operational user
requirements to include interoperability as a Key Performance
E126.96.36.199. Incorporates both materiel (acquisition or
procurement) and non-materiel (doctrine, organizational, training,
leadership, personnel, or facilities) solutions.
E188.8.131.52. Verifies solutions sets in formal tests or
evaluates interoperability Key Performance Parameters and verifies overall
IT and NSS interoperability throughout a system's life.
Oversight. Senior executive-level review of programs to ensure
compliance with policy and attainment of broad program goals.
E2.1.46. Requirement. The need of an
operational user initially expressed in broad operational capability terms in
the format of a MNS. It progressively evolves to system-specific performance
requirements in the ORD.
Signals Intelligence (SIGINT). A category of intelligence
comprising, either individually or in combination, all Communications
Intelligence (COMINT), Electronics Intelligence (ELINT), and Foreign
Instrumentation Signals Intelligence (FISINT).
Spectrum Supportability. The assurance that the necessary
frequencies and bandwidth are available to military systems in order to
maintain effective interoperability in the operational electromagnetic
environment. It includes spectrum certification, host nation coordination,
frequency assignment, and electromagnetic compatibility.
Standards Compliance. Confirmation that IT and NSS has undergone
standards testing and exhibits a specified degree of standards conformity.
E2.1.50. Standards Conformance Certification.
Confirmation by DISA that an IT and NSS has undergone information
technology standards testing and exhibits IT standard base implementation. IT
standards include standards for information processing, information content
(such as standard data definitions), information formats, and information
Supportability. The ability of existing and planned IT, including
NSS, systems and infrastructure components to aid, protect, complement, and
sustain development or operation of the system being acquired.
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 degrades the performance or capabilities of the whole.
System Standards Profile. A system-specific list of all technical
standards and guidelines for their use. To meet IT and NSS interoperability
requirements, the system standards profile should be built from applicable
standards drawn from the DoD Joint Technical Architecture.
E2.1.54. Tactical SIGINT System . All SIGINT
systems developed for use by U.S. Forces.
Test and Evaluation (T&E). The act of generating data during
the research and development of emerging systems and the creation of
information through analysis that is useful to technical personnel and
decision-makers for reducing design and acquisition risks. The process that
gauges progress by measuring systems against requirements and specifications
and analyzing the results.
Universal Reference Resource (URR). Reference models and
information standards that 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.
E2.1.57. Validation. An authoritative act or
process of supporting or corroborating whether IT and NSS interoperability and
supportability requirements are appropriate.
E2.1.58. Verification. The act of
establishing whether IT and NSS interoperability requirements are accurate,
measurable, supportable, and adequately reflected in a system or family of
systems' acquisition strategy, test and evaluation plan, or in non-materiel or
non-traditional acquisition IT and NSS interoperability