Accreditation. The process by which an IT and NSS are evaluated for meeting
security requirements to maintain the security of both the information and the
information systems. A designated accreditation authority (DAA) is named for
each system. Co-DAAs will accredit IT and NSS in certain cases involving
interoperability or integration of multiple systems.
Acquisition Category (ACAT). Categories established to facilitate
decentralized decision making as well as execution and compliance with
statutorily imposed requirements. The categories determine the level of
review, decision authority, and applicable procedures. DOD 5000.2-R, Part 1,
provides the specific definition for each acquisition category (ACAT I through
ACAT I. A major defense acquisition program (MDAP) subject to Defense
Acquisition Board oversight and estimated by the USD(AT&L) to require an
eventual total expenditure of more than $355 million in RDT&E funds, or
$2.135 billion in procurement funds measured in FY 1996 constant dollars.
ACAT IA. A major automated information system (MAIS) acquisition program
that is estimated to require program costs in any single year in excess of $30
million, total program costs in excess of $120 million, or total lifecycle
costs in excess of $360 million (FY 1996 constant dollars).
ACAT IAC. A major automated information system acquisition program for
which the DOD chief information officer (CIO) has delegated milestone decision
authority (MDA) to the component acquisition executive (CAE) or component CIO.
The “C” (in ACAT IAC) refers to component.
ACAT IAM. A major automated information system (MAIS) acquisition program
for which the MDA is the DOD CIO.
ACAT IC. A major defense acquisition program subject for which the MDA is
the DOD component head, or if delegated, the DOD component acquisition
executive (CAE). The “C” refers to component.
ACAT ID. MDAP for which the MDA is USD (AT&L). The “D” refers to the
Defense Acquisition Board (DAB), which advises the USD(AT&L) at major
Administrative comments. Administrative comments to correct what appear to
be typographical or grammatical errors.
Architecture. The structure, relationships,
principles and guidelines that governs component design and evolution.
Automated Information System (AIS). A combination of computer hardware and
computer software, data, and/or telecommunications that performs functions
such as collecting, processing, storing, transmitting and displaying
information. Excluded are computer resources, both hardware and software, that
are: physically part of, or dedicated to, or essential in real time to the
mission performance of weapons systems; used for weapon system specialized
training, simulation, diagnostic test and maintenance, or calibration; or used
for research and development of weapon systems.
Certification. A statement of adequacy provided by a responsible agency for
a specific area of concern in support of the validation process. Certification
consists of three forms of capability confirmation -- first, one that
addresses system interoperability requirements; second, one that addresses
supportability; and third, one that addresses total lifecycle oversight of
warfighter interoperability requirements. The two J-6 certifications and
validation are discussed below.
a. J-6 Developmental and Production Capabilities Interoperability
Certification. This certification occurs prior to each acquisition milestone
(B, C). The J-6 certifies ORDs, CDDs, CPDs and ISPs regardless of ACAT
level, for conformance with joint IT and NSS policy and doctrine and
interoperability standards. As part of the review process, J-6 requests
assessments from the Services, OSD, DISA and DOD agencies.
b. J-6 Supportability Certification. The J-6 certifies to OASD(NII) that
programs, regardless of ACAT, adequately address IT and NSS infrastructure
requirements, the availability of bandwidth and spectrum support, funding,
personnel, and identify dependencies and interface
systems. As part of the review process, J-6 requests supportability
assessments from DISA and DOD agencies. J-6 conducts a supportability
certification for CPD, prior to Milestone C for submission to OASD(NII) as
part of the CPD review process.
c. J-6 Interoperability System Validation. The J-6 validation is
intended to provide total lifecycle oversight of warfighter capabilities
interoperability. The J-6 validates the DISA (JITC) interoperability system
test certification, which is based upon a joint certified NR-KPP, approved
in the CDD, CPD and ISP. The validation will occur after receipt and
analysis of the DISA (JITC) interoperability system test certification. The
J-6 will issue an interoperability system certification memorandum to the
respective Services, agencies, and developmental and operational testing
C4I Support Plans (C4ISP). A document that provides a window into a
specific system development program through which can be seen any shortfalls
in the intelligence support, IT and NSS required for each phase of the systems
Capability Gaps. Those synergistic
resources (DOTMLPF) that are unavailable but potentially attainable to the
operational user for effective task execution.
Capability Production Document (CPD). A
document that addresses the production elements specific to a single increment
of an acquisition program.
Document (CRD). A document that contains capabilities-based
requirements that facilitates the development of CDDs and CPDs by providing a
common framework and operational concept to guide their development.
Coalition interface. Any interface that
passes information between one or more US IT and NSS and one or more coalition
partner IT and NSS.
Combined interface. Any interface that
passes information between one or more US IT and NSS and one or more allied IT
Computer resources. Components physically
part of, dedicated to, or essential in real time to mission performance; used
for weapon system specialized training, simulation, diagnostic test and
maintenance or calibration; or used for research and development of weapon
Communities of Interest (CoI).
Collaborative groups of users who must exchange information in pursuit of
their shared goals, interests, missions, or business processes, and who
therefore must have shared vocabulary for the information they exchange
(source: DCIO DOD Net-Centric Data Strategy, dated 9 May 2003)
Critical comments. Critical comments will
cause non-concurrence in a document if comments are not satisfactorily
resolved. During a flag-level review, persons commenting are required to
contact and coordinate critical comments with document submitters prior to
submission of the
Defense Information Infrastructure (DII).
Outdated term: the DII is the web of communications networks, computers,
software, databases, applications, weapon system interfaces, data, security
services, and other services that meet the information processing and
of DOD users across the range of military operations. It
a. Sustaining base, tactical, IT and NSS.
b. Physical facilities used to collect, distribute,
store, process, and display voice, data and imagery.
c. Applications and data engineering tools, methods and
processes to build and maintain the software that allow command and control
(C2), intelligence, surveillance, reconnaissance, and mission support users
to access and manipulate, organize and digest proliferating quantities of
d. Standards and protocols that facilitate
interconnection and interoperation among networks.
e. People and assets, which provide the integrating
design, management and operation of the DII, develop the applications and
services, construct the facilities and train others in DII capabilities and
f. DOD Information Technology Standards Registry (DISR).
g. Replacement for the DOD Joint Technical Architecture
(JTA). It will also be accessible via the Internet. DOD Joint Technical
Architecture (DOD JTA). The DOD JTA provides DOD systems with the basis for
the needed seamless interoperability. The DOD JTA defines the service areas,
interfaces, and standards (DOD JTA elements) applicable to all DOD systems.
Its adoption is mandated for the management, development and acquisition of
new or improved systems throughout DOD. The DOD JTA consists of the core,
four domains, and numerous subdomains. The DOD JTA core contains the minimum
set of DOD JTA elements applicable to all DOD systems to support
interoperability. Standards and guidelines contained in the DOD JTA are
stable, technically mature and publicly available. In addition, the JTA
online system provides a Web-based capability for creating DOD JTA standard
complaint profiles that can be used to build a TV-1 or TV-2. (https://disronline.disa.mil).
ASD(NII) is currently transforming the JTA to the DOD Information Technology
Standards Registry (DISR) to better support the business and warfighting
domains. It will also be accessible via the Internet.
compatibility (EMC). The ability of systems, equipment and devices that
use the electromagnetic spectrum to operate in their intended operational
environments without suffering unacceptable degradation or causing
unintentional degradation because of electromagnetic radiation response. It
involves the application of sound electromagnetic Spectrum Supportability;
system, equipment, and device design configuration that ensures
interference-free operation; and clear concepts and doctrines that maximize
environmental effects (E3). E3 is the impact of the electromagnetic
environment upon the operational capability of military forces, equipment,
systems, and platforms. It encompasses all electromagnetic disciplines,
including compatibility, interference; vulnerability, pulse; protection;
hazards of radiation to personnel, ordnance, and volatile materials; and
natural phenomena effects, of lightning and p-static.
Family-of-systems. A set or arrangement
of independent systems that can be arranged or interconnected in various ways
to provide different capabilities. The mix of systems can be tailored to
provide desired capabilities dependent on the situation.
Global Information Grid (GIG). The
globally interconnected, end-to-end set of information capabilities associated
processes and personnel for collecting, processing, storing, disseminating,
and managing information on demand to warfighters, policy makers, and support
personnel. The GIG includes all owned and leased communications and computing
systems and services, software (including applications), data, security
services and other associated services necessary to achieve information
superiority. It also includes National Security Systems as defined in section
5142 of the Clinger-Cohen Act of 1996. The GIG supports all Department of
Defense, National Security Systems, and related Intelligence Community
missions and functions (strategic, operational, tactical and business), in war
and in peace. The GIG provides capabilities from all operating locations
(bases, posts, camps, stations, facilities, mobile platforms and deployed
sites). The GIG provides interfaces to coalition, allied, and non-DOD users
Information assurance (IA). Information
operations that protect and defend information and information systems by
ensuring their availability, integrity, authentication, confidentiality, and
nonrepudiation. This includes providing for restoration of information systems
by incorporating protection, detection, and reaction capabilities. (Joint
Information exchange requirements.
Information exchange requirements (IERs) characterize the information
exchanges to be performed by the proposed system(s). For CDDs, top-top
leveltop level IERs are defined as those information exchanges that are
between systems of combatant command/Service/agency, allied, and coalition
partners. For CPDs, top level IERS are defined as those information exchanges
that are external to the system (i.e., with other combatant
commands/Services/agencies, allied and coalition systems). IERs identify
who exchanges what information with
whom, why the information is necessary, and
how the information exchange must occur. Top-level IERs
identify warfighter information used in support of a particular
mission-related task and exchanged between at least two operational systems
supporting a joint or combined mission. The quality (i.e., frequency,
timeliness, security) and quantity (i.e., volume, speed, and type of
information such as data, voice, and video) are attributes of the information
exchange included in the information exchange requirement.
Information Support Plan (ISP). Used by
program authorities to document the IT and NSS needs, objectives, interface
requirements for all non-ACAT and fielded programs. ISPs should be kept
current throughout the acquisition process and formally reviewed at each
milestone, decision reviews and whenever the operational concepts, and IT and
NSS support requirements change.
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. Information technology includes computers, ancillary
equipment, software, firmware, and similar procedures, services (including
support services), and related resources. Information technology does not
include any equipment that is acquired by a federal contractor incidental to a
Initial Capabilities Document (ICD) -
Documents the need for a materiel solution to a specific capability gap
derived from an initial analysis of alternatives executed by the operational
user and, as required, an independent analysis of alternatives. It defines the
capability gap in terms of the functional area, the relevant range of military
operations, desired effects, and time.
Integrated Architecture. An architecture
consisting of multiple views or perspectives (Operational View, Systems View,
and Technical Standards View) that facilitates integration and promotes
interoperability across family of systems and system of systems and
compatibility among related architectures. An architecture description that
has integrated Operational, Systems, and Technical Standards Views with common
points of reference linking the Operational View and the Systems View and also
linking the Systems View and the Technical Standards View. An architecture
description is defined to be an integrated architecture when products and
their constituent architecture data elements are developed such that
architecture data elements defined in one view are the same (i.e., same names,
definitions, and values) as architecture data elements referenced in another
Intelligence certification. Confirmation
by DIA of the availability, suitability, and sufficiency of intelligence to
support a system or program. Intelligence certification also provides: (1) an
assessment of the impact of a system or program on joint intelligence
strategy, policy, architectural planning, and needs of the warfighter and (2)
an evaluation of open systems architectures, interoperability, and
compatibility for intelligence handling and intelligence-related information
systems. This certification will occur as a prerequisite for the system
acquisition process and at each acquisition milestones.
Interim Certificate to Operate (ICTO).
Authority to field new systems or capabilities for a limited time, with a
limited number of platforms to support developmental efforts, demonstrations,
exercises, or operational use. The decision to grant an ICTO will be made by
the MCEB Interoperability Test Panel based on the sponsoring component's
initial laboratory test results and the assessed impact, if any, on the
operational networks to be employed.
Interoperability. a. The ability of
systems, units, or forces to provide services to and accept services from
other systems, units, or forces and to use the services so exchanged to enable
them to operate effectively together, and b. The condition achieved among
communications electronics systems or items of communications-electronics
equipment when information or services can be exchanged directly and
satisfactorily between them or their users. The degree of interoperability
should be defined when referring to specific cases. For the purposes of this
instruction, the degree of interoperability will be determined by the
accomplishment of the proposed IER fields.
Interoperability Watch List (IWL).
Established by the USD(AT&L), the ASD(NII)/DOD CIO, the Chairman of the
Joint Chiefs of Staff, and the Commander, U.S. Joint Forces Command to provide
DOD oversight for those IT and NSS activities for which interoperability is
deemed critical to mission effectiveness, but interoperability issues are not
being adequately addressed. IT and NSS considered for the IWL may be
preacquisition systems, acquisition programs (any ACAT), already fielded
systems, or combatant commander-unique