Joint. Connotes activities, operations,
organizations, etc., in which elements of two or more Military Departments
participate. (Joint Publication 3-13).
Joint C4ISR Architecture
Planning/Analysis System (JCAPS). DOD approved static architecture tool for
manipulating and conducting analysis of operational and systems
Joint integrated architecture. An
integrated architecture that establishes the basis for rapidly acquiring
affordable and evolving joint warfighting capabilities through collaborative
planning, analysis, assessment, and decision making.
Joint interface. An IT and NSS interface
that passes or is used to pass information between systems and equipment
operated by two or more combatant commanders, Services, or agencies.
JROC special interest. Programs
identified by the JROC Secretary as being of interest to the JROC for
oversight even though they do not meet the ACAT I cost thresholds or have been
designated as ACAT ID.
Levels of Information System
Interoperability (LISI). A model that is applied to information systems to
gain a figure of interoperability between systems. Within the LISI model,
systems are evaluated by their use, application, sharing and/or exchange of
common procedures (to include technical standards), software applications,
infrastructure and data. The resultant value, from 0 to 4, indicates the
interoperable maturity levels of Isolated (0), Connected (1), Functional (2),
Domain (3) and Enterprise (4).
Key Interface. Interfaces in functional
and physical characteristics that exist at a common boundary with
co-functioning items, systems, equipment, software and data. They are
designated as a Key Interface when one or more of the following criteria
a. The interface spans
organizational boundaries. Different entities (service,
agency, organization) have ownership and authority over the hardware and
software capabilities on either side of the boundary,
b. The interface is mission
critical. Data from joint organizations, multiple services, and/or
multiple agencies/organizations must move across the interface to satisfy
joint information flow requirements. If systems are not interoperable at
that interface, the ability to accomplish the mission is endangered.
c. The interface is difficult or
complex to manage.
d. There are capability,
interoperability, or efficiency issues associated with the
e. The interface impacts
multiple acquisition programs, usually more than two (e.g. network
points of presence, many-to-many or one-to-many connections).
f. The interface is
vulnerable or important from a security
Key Interface Profile (KIP). An
operational functionality, systems functionality and technical specifications
description of the Key Interface. The profile consists of refined Operational
and Systems Views, Interface Control Document/Specifications, Engineering
Management Plan, Configuration Management Plan, Technical View with SV-TV
Bridge, and Procedures for Standards Conformance and Interoperability
Key performance parameters (KPPs). Those
capabilities or characteristics considered essential for successful mission
accomplishment. Failure to meet a system or program's 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 system or program's KPP
threshold can be cause for the family-of-systems or system-of-systems concept
to be reassessed or the contributions of the individual systems to be
reassessed. KPPs are validated by the JROC. KPPs are included in the
acquisition program baseline.
Milestone decision authority (MDA). The
individual designated in accordance with criteria established by the
USD(AT&L), or by the ASD (NII) for acquisition programs, to approve entry
of an acquisition program into the next phase.
Milestones. Major decision points that
separate the phases of an acquisition program.
Mission need. A deficiency in current
capabilities or an opportunity to provide new capabilities (or enhance
existing capabilities) through the use of new technologies. They are expressed
in broad operational terms by the DOD components.
Mission needs statement (MNS). A
formatted non-system-specific statement containing operational capability
needs and written in broad operational terms. It describes required
operational capabilities and constraints to be studied during the Concept
Exploration and Definition Phase of the Requirements Generation Process.
(Joint Publication 3-13).
National Security Systems (NSS).
Telecommunications and information systems operated by the Department of
Defense -- the functions, operation, or use of which (1) involves intelligence
activities; (2) involves cryptologic activities related to national security;
(3) involves the command and control of military forces; (4) involves
equipment that is an integral part of a weapon or weapons systems; or (5) is
critical to the direct fulfillment of military or intelligence missions.
Subsection (5) in the preceding sentence does not include procurement of
automatic data processing equipment or services to be used for routine
administrative and business applications (including payroll, finance,
logistics and personnel management applications).
Net-Centricity. Net-centricity enables
user access and use of resources both collaboratively and asynchronously,
regardless of time and place. It is the ability of a program or system to
integrate with, offer services to, and exploit the services of a net-centric
Net Centric. Exploitation of advancing
technology that moves from an applications-centric to a data-centric paradigm
- that is, providing users the ability to access applications and services
through Web services – an information environment comprised of interoperable
Net Centric Operations and Warfare
(NCOW). Describes how DOD will conduct business operations, warfare, and
enterprise management. It is based on the concept of an assured, dynamic, and
shared information environment that provides access to trusted information for
all users, based on need, independent of time and place. It is characterized
by assured services, infrastructure transparency (to the user), independence
of data consumers and producers, and metadata supported by information
discovery, protection and mediation. This fundamental shift from
platform-centric warfare to net-centric warfare provides for an Information
Superiority-enabled concept of operations. The NCOW RM provides a common
taxonomy and lexicon of NCOW concepts and terms, and architectural
descriptions of NCOW concepts. It represents an important mechanism in DOD
transformation efforts, establishing a common framework for net-centricity. It
will enable capability developers, program managers, and program oversight
groups to move forward on a path toward a transformed, net-centric enterprise.
Net Centric Operations and Warfare
Reference Model (NCOW RM). Reference Model (NCOW RM). The NCOW RM describes
the activities required to establish, use, operate, and manage the net-centric
enterprise information environment to include: the generic user interface, the
intelligent-assistant capabilities, the net-centric service capabilities (core
services, Community of Interest (CoI) services, and environment control
services), and the enterprise management components. It also describes a
selected set of key standards that will be needed as the NCOW capabilities of
the Global Information Grid (GIG) are realized. The NCOW RM represents the
objective end-state for the GIG. This objective end-state is a
service-oriented, inter-networked, information infrastructure in which users
request and receive services that enable operational capabilities across the
range of military operations; DOD business operations; and Department-wide
enterprise management operations. The NCOW RM is a key compliance mechanism
for evaluating DOD information technology capabilities and the Net Ready Key
Net-Ready. DOD IT/NSS that meets required
information needs, information timeliness requirements, has information
assurance accreditation, and meets the attributes required for both the
technical exchange of information and the end-to-end operational effectiveness
of that exchange. DOD IT/NSS that is Net-Ready enables warfighters and DOD
business operators to exercise control over enterprise information and
services through a loosely coupled, distributed infrastructure that leverages
service modularity, multimedia connectivity, metadata, and collaboration to
provide an environment that promotes unifying actions among all participants.
Net-readiness requires that IT/NSS operate in an environment where there
exists a distributed information processing environment in which applications
are integrated; applications and data independent of hardware are integrated;
information transfer capabilities exist to ensure seamless communications
within and across diverse Media; information is in a common format with a
common meaning; there exist common human-computer interfaces for users; and
there exists effective means to protect the information. Net-Readiness is
critical to achieving the envisioned objective of a cost-effective, seamlessly
integrated environment. Achieving and maintaining this vision requires
a. Within a Joint Task Force/combatant
command area of responsibility (AOR).
b. Across combatant command AOR
c. Between strategic and tactical
d. Within and across Services and
e. From the battlefield to the
f. Among US, Allied, and Coalition
g. Across current and future
Net-Ready Key Performance Parameter
(NR-KPP). The NR-KPP assesses information needs, information timeliness,
information assurance, and net-ready attributes required for both the
technical exchange of information and the end-to-end operational effectiveness
of that exchange. The NR-KPP consists of verifiable performance measures and
associated metrics required to evaluate the timely, accurate, and complete
exchange and use of information to satisfy information needs for a given
capability. The NR-KPP is comprised of the following elements: a. Compliance
with the Net-Centric Operations and Warfare (NCOW) Reference Model (RM), b.
Compliance with applicable GIG Key Interface Profiles (KIPs), c. Verification
of compliance with DOD information assurance requirements, d. Supporting
integrated architecture products required to assess information exchange and
use for a given capability.
Net-Ready KPP Assessment. The Net-Ready
KPP Assessment determines the impacts, risks, and vulnerabilities of fielding
secure, interoperable, supportable, sustainable and usable (SISSU) systems to
the warfighter. Parameters assessed include: network security, network impact,
compatibility with the infrastructure, infrastructure requirements, spectrum
support, security policy compliance, DISR standards compliance, communications
and information manpower, training, logistics support, schedule and funding. A
system that has been assessed and determined to be supportable from a
communications and information perspective, and any impacts, risks and
vulnerabilities that it may present to the enterprise are deemed to be
acceptable or manageable is Net Ready.
Network warfare simulation (NETWARS). The
standard DOD approved communications simulation tool. Combatant commanders,
Services and agencies use NETWARS for all communications modeling
Non-Acquisition (Non-ACAT) Program. An
effort that does not directly result in the purchase of a system or equipment
for operational employment (e.g., science and technology programs, concept
exploration or advanced development of potential acquisition programs).
Operational requirements document (ORD).
A formatted statement-containing performance and related operational
parameters for the proposed concept or system. Prepared by the user or user's
representative at each milestone beginning with milestone I. Upon publication
of CJCSI 3170.01C, new ORDs will be accepted for only 90 days. Existing ORDs
will continue to be used until absorbed into the new JCIDS (see reference a).
Originator. A DOD component or
operational command that initiates a MNS. The originator may or may not be the
Procedural interface. The methods and
procedures employed to establish an interconnection within and between systems
or equipment and to transfer information within or between systems or
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 CDD.
Seamless IT and NSS environment. An
electronic environment that allows data to be accessed by the warfighter
without regard to physical or electronic boundaries.
Service deployment plans and fielding
plans. Plans that describe the evolution from current capabilities to the full
operational capability for new or modified IT and NSS. Included are fielding
schedules, plans, locations, and associated time-phased interoperability
requirements with current and planned systems of other DOD
components or allies.
Spectrum certification. The process by
which development or procurement of communication-electronics systems,
including all systems employing satellite techniques, will be reviewed and
certified for system compliance with Spectrum Supportability policy,
allocations, regulations, and technical standards to ensure that radio
frequency spectrum is available. Additionally, the predicted degree of
electromagnetic compatibility between the proposed system and
spectrum-dependent systems; and the possible need for and evaluation
of the results of prototype electromagnetic compatibility testing will be
Spectrum Supportability. The
determination as to whether the electromagnetic spectrum necessary to support
the operation of spectrum-dependent equipment or system during its expected
lifecycle is, or will be, available (that is, from system development, through
developmental and operational testing, to actual operation in the
electromagnetic environment.) The assessment of equipment or system as having
“spectrum supportability is based upon, as a minimum, receipt of equipment
spectrum certification, reasonable assurance of the availability of sufficient
frequencies for operation, and consideration of electromagnetic compatibility
Standardization approach. A statement(s),
which demonstrates a commitment to use DOD, approved standards. For example,
“The system must comply with applicable information technology standards
contained in the DOD Information Technology Standards Registry (DISR) current
Standards. Standards as referenced in
this instruction are information technology (IT) standards and include
specifications, profiles, protocols, implementation conventions, Federal
Information Processing Standards (FIPs), Military Standards (MIL-STDs),
Defense Performance Specifications (MIL-PRFs), NATO Standardization Agreements
(STANAGs), Allied Communications Publications (ACPs), Allied Data Publications
(ADatP), guidelines, commercial item descriptions, standardized drawings,
handbooks, manuals, tools, and other related documents relevant to the
application and use of information and communications technology. They are
software and hardware standards that are used for intelligence collection,
data and information processing, information transfer, and information
presentation/ dissemination. IT standards provide technical definitions for
information system processes, procedures, practices, operations, services,
interfaces, connectivity, interoperability, information formats, information
content, interchange, and transmission of transfer. IT standards apply during
the development, testing, fielding, enhancement, and lifecycle maintenance of
DOD information systems. Recognized standards include those produced as
non-governmental national or international standards (e.g., ANSI and ISO),
trade association and professional society standards (e.g., IEEE), Federal
standards (e.g., FIPS), military standards, and multinational treaty
organization standardization agreements.
Substantive comment. Substantive comments
are provided because sections in the document appear to be or are potentially
unnecessary, incorrect, incomplete, misleading, confusing, or inconsistent
with other sections.
Supportability. The level 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 requirements between systems.
SV-1. High-level system interface
System. For use in this publication, the
term “system” refers to a system or program. A practical definition is that a
“system” will follow the complete Joint Capability Integration and Development
System (JCIDS) (Requirements Generation System (RGS)) process.
Technical View. An architecture view that
describes in engineering terms how to tie systems together. It consists of
standards that define and clarify the individual systems technology and
Validation. The review of documentation
by an operational authority other than the user to confirm the operational
capability. Validation is a precursor to approval.
Validation Authority. The individual
within the DOD components charged with overall capability definition and
validation. The Vice Chairman of the Joint Chiefs of Staff, in the role as the
Chairman of the JROC, is the validation authority for all potential major
defense acquisition programs. The validation authority for JCIDS issues is
dependent upon the JPD of the program or initiative as specified below:
a. JROC Interest - JROC
is validation authority.
b. Joint Impact - The
lead FCB is the validation authority.
c. Joint Integration -
The sponsor is the validation authority.
d. Independent - The
sponsor is the validation authority.