The Largest Security-Cleared Career Network for Defense and Intelligence Jobs - JOIN NOW


Joint Network Management System (JNMS)

Primary Purpose The JNMS is a CINC and Commander, Joint Forces

(CJF), joint communications planning and

management system. It provides communication

planners with the capabilities to conduct high

level planning (war planning); detailed planning

and engineering; monitoring; control and

reconfiguration; spectrum planning and

management; and security of systems and networks

supporting joint operations. The benefits

provided by these increased capabilities include:

enhanced force-level situational awareness

(shared view of the network); enhanced

flexibility to support the commander's intent;

better utilization of scarce spectrum resources;

and increased security of critical systems and

networks. As an enabler for information

superiority as-well-as command and control, the

JNMS serves as the commanders' "brain center" for

the systems and networks supporting his forces.

It ensures C4I unity of effort, exploitation of

Total Force capabilities, proper positioning of

critical information and allows for its fusion.

Sub-Functions High-Level Planning (CINC/JTF level):

Create/modify databases for C4I equipment

(Threshold) and organizations (units).

Define the network topology based on sites

(Threshold) and by organizations (units).

Create/modify subordinate unit tasks,

responsibilities, schedules and track


Detailed Planning and Engineering: Provide the

capability to conduct detailed joint C4 network

planning, engineering, activation (and


Perform network planning and engineering for a

notional MTW JTF network (Internet Protocol (IP)

data, Super High Frequency (SHF), and terrestrial



Graphically display network configurations and

status changes in near real-time.

Provide the warfighter access to JNMS C4 status

information to enhance.

Conduct performance analysis.

Control and Reconfiguration:

Perform network device


Generate and process change orders.

Perform automated fault management.

Model, evaluate, and optimize proposed network


Spectrum Planning and Management:

Assign and deconflict frequency resources.

Generate and distribute JSOI and the JRFL.

Perform automated communications propagation



Display regional Defensive Information Operations

IP device status near real-time. (Threshold).

Receive, process, and display status and event information from Information Assurance (IA) Management Systems associated with designated networks.

Correlate IA events with respect to their impact on joint networks.

Support Electronic Key Management Systems.

Equipment Requirements Because the JNMS software can be run on a variety

of hardware platforms (based on JTA/DII COE

compliance and minimum specified system

requirements to be provided by the materiel

developer), hardware support requirements are

considerations to be used in selecting a

platform. The PM will provide users with a set

of minimum requirements for hardware to run the

JNMS. Government off-the-shelf (GOTS) software

packages included in the JNMS must be Y2K, DII

COE complaint and supported by their respective

program offices as part of the post-development

software support (PDSS) process. The JNMS

program office responsibility is the integration

of the various GOTS and licensed commercial

off-the-shelf (COTS) products, as well as the

maintenance of the COTS software licenses. The

PM will make every effort to secure Enterprise

licensing agreements with COTS


Connectivity Requirements The JNMS is supported by Service/Agency level

functional area programs in spectrum management,

information security (INFOSEC), information

dissemination, military satellite communications

(MILSATCOM), DISN common-user transport systems,

switching, transport and through post deployment

software support (PDSS) centers.

Crypto Requirements No additional requirements.

Normal Locations JNMS User Community. The CINC will utilize JNMS

to support a remote (deployed) JTF Joint

Communications Control Center (JCCC). Joint

level managers and Service component headquarters

level System Controls (SYSCONs) will use the

JNMS (See Figure 1-1). Each communications unit

responsible for providing these SYSCONs must be

equipped with a JNMS capability to deploy with

the unit. Because the JNMS is scalable and

modular, the Services may select a subset of JNMS

capabilities to employ at units below the

component SYSCON. Other DOD agencies may also

use the JNMS to manage their systems that are

supporting the joint backbone.

Information Managed The JNMS will provide CINC and deployed JTF level

communication planners with the capability to

perform tasks associated with the following


High Level Planning:

Creation/Editing and/or loading of data base.

Definition of network sites and units.

Assignment of responsibilities and schedules.

Generation and distribution of planning data

(Annex K, Joint CEOI, Communications Service

Requests (CSRs), Other data).

Detailed Planning, Engineering, Activation and


Circuit switch planning and engineering.

ATM planning and engineering.

DMS planning and engineering.

Commercial and military satellite communications

systems planning and engineering for designated

ranges, including UHF, UHF DAMA, SHF, C, X, Ku,

Ka and EHF.

Data network planning and engineering.

Single channel networks planning and engineering.

Message switch planning and engineering.

Transmission systems planning and engineering.

Generation and distribution of planning and

engineering data.

Link and network activation.

Gateways between networks.


Collection of data from equipment and network.

Data analysis.

Data base updates.

Generation and distribution of data and reports.

Control and Reconfiguration:

Network device configuration.

Processing of incoming data.

Generation and evaluation of alternative


Implementation of appropriate responses.

Spectrum Planning and Management:

Information management.

Spectrum engineering.

Allotment/assignment of frequencies.


EMC analysis.

EMI analysis.


Formulate network security requirements.

Physical security.

User security.

Information Assurance (IA).

COMSEC/Electronic Protection (EP).

The last two functional areas (spectrum planning

and management, and security) intersect the four

other functional areas.

Products Created Refer to Information Managed.

Lead Service/Contractor The JNMS supports the following TRADOC Future

Operational Capabilities (FOCs) defined in TRADOC

PAM 525-66: TR 97-013. Network Management; TR

97-015. Common Terrain Portrayal; TR 97-019.

Command and Control Warfare (C2W) (a) Information

Protection; TR 97-048. Performance Support

Systems; TR 97-049. Battle Staff Training and

Support; TR 97-050. Joint, Combined and

Interagency Training; TR 97-053. Embedded

Training (ET) and Soldier-Machine Interface; TR

97-057. Modeling and Simulation.

Current Fielding Status An interim solution, DISA's Joint Defense

Information Infrastructure Control System -

Deployed (JDIICS-D), is now being fielded as the

JNMS (v1) and is to be replaced with the JNMS,

(v2), using an industry driven phased, modular

approach. The Initial Operating Capability (IOC)

will be considered complete when the JNMS is

fielded to a geographical CINC, its respective

CINC Components, a JTF Headquarters and JTF

Component HQs; the personnel are fully trained in

its operations and maintenance, and logistics

support is in place. For IOC, the total number

of the JNMSs is 36 for a geographical CINC, i.e.,

18 per CINC and CINC components; and an

additional 18 for a CJTF and JTF components. The

36 JNMS suites support network management for

the three classification levels and networks:


SECRET-SCI (JWICS). For IOC, each JNMS suite

must meet all stated threshold requirements. The

target date for the IOC is 4QFY03. If the IOC

is not met, the interim system may become

non-supportable and cause a capabilities

shortfall for all CINCs. Full Operational

Capability is considered to be a JNMS capability

to all CINCs, CINC Components, CJTF and JTF

Components to include: fielding, personnel

training in operations and maintenance, and

logistics support. Joint Network Management will

continue to evolve with network technologies and

standards, which will require software and

hardware, upgrades with evolved personnel

training requirements and maintenance support.

Known Problems Manpower/Personnel.


Human Engineering.

DIICOE Compliance Rating The JNMS must be Joint Technical Architecture

(JTA) and DII COE compliant.

- DII COE Level 6 (Threshold)

- DII COE Level 8 (Objective)

The JNMS will incorporate joint communications

network management and planning functions across

the DII, down to and including JTF component

headquarters. Joint communications network

management and planning functions by component

headquarters will be interoperable through or

integrated into the JNMS. Services are

responsible to ensure that their internal network

management systems are interoperable with the

JNMS through the use of standard protocols and

open systems architecture. Service

configurations of the JNMS must be interoperable

and perform prescribed functions. The JNMS must

be capable of interfacing with allied and

coalition networks. The JNMS must comply with

the applicable provisions of the JTA, to include

DII COE compliance, so as to run on multiple

types of hardware (consistent with the minimum

specified system requirements to be provided by

the materiel developer) and be readily adaptable

to change. The JNMS product will be constantly

improved in an evolutionary manner so that new

technologies and emerging capabilities in joint

network management are incorporated. JNMS

software modules and functionality will be built

in using the DII COE as a guide and will be

reusable and integratable with joint C2 systems.

These conditions will allow the system to adapt

to improvements in the joint communications

infrastructure and advances in technology.

Point of Contact Dwight D. Reed


Joint Staff

J6T - Networks Division

(703) 614-2778 (DSN 224-)

Updated by Captain Michael L. Campbell, USAF, CCSC-01






Join the mailing list