Integrated Tactical Networking Environment (ITNE)
Integrated Tactical Networking Environment (ITNE)
Environment (ITNE)
10 September 2013
UNCLASSIFIED
Agenda
• Purpose
• ITNE Imperatives
• ITNE Complexity
• ITNE Dependencies
• Questions UNCLASSIFIED
UNCLASSIFIED
Purpose
UNCLASSIFIED
UNCLASSIFIED
ITNE Imperatives
UNCLASSIFIED
UNCLASSIFIED
ITNE Capability Development
Methodology
Individual System NET
SA/DP SA/DP NET 16 hrs. 2 session Min 2 ; Max 8 25A, 25B, 25C, 25W, 53A, 250N, Bde HQ None YES
251A, 254A, BTL CPTs, 25U in
charge of LTI planning
WIN-T Inc 2 (BCT) TCN-OM 320 (+80 hrs. crew drills) 1 session min 16 (2 per CI); 25N Bde HQ, Bn FMTV drivers training. (See
max 24 (3 per CI) NMIB and MFP for
technical requirements)
YES
NETOPS 320 (+ 80 hrs. crew drills) 1 session min 17; max 20 25B (8), 25E (1), 25N (1), 25Q Bde HQ See NMIB and MFP. YES
(NOSC-B) (1), 25S (1), 25W (1), 250N (1),
254A(1), 25A(1), 53A(1), 255S
(1), 255N (1) (FROM MER 26 Jul
12)
PoP User 40 hrs. (1 day IB training; 1 session 14 (2 per CI) GPU (Vehicle Crew) Bn Driver training on YES
+ 80 hrs. crew drills) platform.
SNE User 40 hrs. (1 day IB training; Up to 20 students per min 66 (2 per CI); GPU (Vehicle Crew) Co Driver training on YES
+ 80 hrs. crew drills) session. 4 sessions. max 80 platform.
VWP 24 hrs. (1 day IB training; 1 session 20 (2 per CI) GPU (Vehicle Crew) Bde, Bn Driver training on YES
+ 80 hrs. crew drills) platform. CPP NET for CPP
VWPs.
User Support Course 200 hrs. (1 day IB train-ing 1 session 20 25U, 25B, 254A Bde, Bn, Co MRAP driver training. YES
to target MOS 25U; + 480
hrs. crew drills)
Transmission 64 hrs. (+ 80 hrs. crew 1 session 19 25Q, 25S Bde HQ STT Delta Course YES
Operator/Maintainer drills)
Course
Staff Overview
40 hours
2-4 hrs.
1 session
1 session
19 (2 25S STT BCT
level, 2 per TRT)
1-20
25Q, 25S
Senior Leadership
Bde HQ
Bde, Bn None
YES
NO
Estimate Approved
WIN-T Inc 2 (Div) TCN-OM 320 (+80 hrs. crew drills)
Courses
1 session Min 6 (2 per CI);
Max 9
Courses.
25N
ITNE Ontology
Div FMTV drivers training. (See
NMIB and MFP for
technical requirements)
YES
NETOPS 320 (+ 80 hrs. crew drills) 1 session min 17; max 20 25B(6). 25E (2), 25N (2), 25Q Div See NMIB and MFP. YES
VWP
drills)
40 hrs. (1 day IB training;
+ 80 hrs. crew drills)
24 hrs. (1 day IB training;
1 session
1 session
max 6
min 6 (2 per CI);
max 10
min 4 (2 per CI);
GPU (Vehicle Crew)
Div
Driver training on
platform.
Driver training on
YES
YES
+ 80 hrs. crew drills) max 6 platform. CPP NET for CPP
VWPs.
User Support Course 200 hrs. (1 day IB train-ing 1 session 20 25U, 25B, 254A, 255A, 255N Div Driver training on YES
to target MOS 25U; + 480 platform.
hrs. crew drills)
Transmission 64 hrs. (+ 80 hrs. crew 1 session min 9; max 10 25Q, 25S Div STT Delta Course YES
Operator/Maintainer drills)
Course
STT Delta 40 hours 1 session min 9; max 10 25Q, 25S Div YES
Staff Overview 2-4 hrs. 1 session 1-20 Senior Leadership Bde, Bn None NO
Personnel Skill MC 13 Key Leaders Overview
40 hrs.
Two sessions offered
4-20
Bde/Bn Cdr/XO, S3, key staff Bde HQ, Bn
leaders
None
General Purpose CPOF users at Bde HQ, Bn Entry level training for
YES
YES
Work Station (MCWS) Operator Course 2.5 users per box; 120 BDE and BN (25B Bn/Bde Staff Soldiers with no previous
Set Alignment (AKA TMC Client) pax Officer/Warrant Officer/NCO) experience. Also, serves as
the prerequisite CPOF
training to other
Warfighting Functions
(WFFs) (FIRES, LOG, etc.)
CPOF courses under
Collapse/Convergence
strategy.
MC 13 (MCWS and TMC TMC Maintainer 16 hrs. 1 session 5-20 25B at Bn/Bde responsible for Bde HQ, BN None YES
Gateway) Course maintaining/configuring CPOF
MC 13 (TMC Server System Administrator 80 hrs. 1 session Max 5 Bde 53A, 255A, 25B Bde HQ None YES
Suite/BCCS) (Server)
MC 13 Command Web Basic Command Web 8 hrs. 7 session (if necessary; 20 GPU of the Command Web Bde HQ, Bn None YES
web enabled laptop environment. Disadvantaged
users without C2 box) users. Users who have no
availability to C2 in CP.
MC 13 Command Web Command Web 16 hrs. 1 session 20 BDE and BN Engineer officers Bde Bn None YES
Future
MC 13 Command Web 1 session 20 CBRN BDE and BN Officers and Bde, Bn None YES
SIGCoE
Command Web CIRS 16 hrs.
NCO
JTNT JTNT OPNET 80 hrs. 2 sessions Max 20 25A, 25C, 25E, 25N (BN/BDE), Bde, Bn Soldiers already trained on YES
255N AN/PRC154A and AN/PRC-
155 (working on adding
(FAA) NETT Warrior NET Warrior OPNET 40 hrs per session
NETT Warror Maint/Sig
Block to JTNT)
IBCT: 16 sessions total (4 min 15; max 60 All leaders/Soldiers identified In Co, CAV Soldiers already trained on YES
JCIDS
sessions per week in (through BOIP) to receive Nett Trp AN/PRC154A
parallel; 4 weeks total); Warrior system (generally TL
SBCT 20 sessions (4
sessions per week in
and above)
parallel; 5 weeks total)
AN/PRC 154A
AN/PRC-154A
Rifleman Radio
Operator
8 hrs. Enough sessions to train
100% NETT Warrior EUD
and 20% of RR only user.
Max 20 GPU. No MOS or echelon Bde, Bn, Co
requirements
YES
IT Box Approach
COMSEC Key and 4 sessions (2 per day for Complteted AN/PRC 154A
Preset Loading 4 hrs. 2 days) max 10 GPU. SKL operators. Co OPNET; COMSEC Access
list; SECRET Clearance
AN/PRC-155 AN/PRC-155 Manpack 16 hrs. 15 GPU Bde, Bn, Co YES
Operator
AN/PRC-155 24 hrs 4 sessions (40 total 10 25U (Co Commo Sgt, Bn and Bde, Bn, Co AN/PRC-155 Manpack YES
Force Structure
(Manpack) FLMNET trained) Bde Retrans, Bn S6 25U, 25U10 Operator NET
and 25U20 at BDE); other 25
series depending on position;
other MOS retrans
6 UNCLASSIFIED
UNCLASSIFIED ITNE Complexity
(SDR Platform Environment)
Raytheon
(SINCGARS/SRW/Mid-Tier) System
OSI Harris Design
Networking
and Link Harris types of parameters
Army
State Layer parameter settings (default) Req
Process
Radio Operating System
(OS)
Exelis
System
General Design
Dynamics
Harris Memory Capacity
Army
Chip Design Req
Process
OSI
Motherboard circuitry
Physical Radio Physical Layer Exelis
Layer Transmission subsystem System
General Design
Dynamics
* Additional ITNE components not illustrated in this depiction include routers, cross domain solutions, gateways, mission command
mobile/mounted applications, networked and non-networked ancillary devices, and the Network Operations (NetOps) system
7 UNCLASSIFIED
ITNE Complexity
(NetOps Processes)
J-TNT
J-TNT
UNCLASSIFIED
ITNE
Concept of Operations
9 UNCLASSIFIED
UNCLASSIFIED
ITNE Concept of Operations
(CONOPS) - Development
Capability Set and ONS Fielding
Lessons Learned TTPs Emerging Concepts
ONS ONS CS 13 CS 13 CS 13 CS 13
173rd ABCT 75th Ranger RGT 10th MTN DIV 101st DIV 3rd ID 1st AD
Doctrine
Lessons Learned TTPs Emerging Concepts
Signal Operations Army Enterprise NetOps CONOPS Army Planning Army Operations
Battalion SINCGARS
Battalion WNW
... ...
... Company SINGARS ...
Lower Tier
Platoon SRW Platoon SRW
Platoon SRW Platoon SRW Mid Tier
Company WNW
Figure does not depict the narrowband SATCOM interoperability points within the Lower and Mid tier
ITNE nor the celestial, aerial, and terrestrial connectivity points with higher headquarter elements.
ITNE Vignettes
Initial Entry Operations Phase III (HIC) Operations
Appendices
A B C D E F G H I J K L M N O
Acronyms Glossary References Multinational Radio Waveform MC Apps Ancillary ITNE Aviation UTR ITNE TTPs Vignette CS 13
Interoperability Platforms Applications Mngt Devices Netops Integration Help Desk Information DTPs
Mngt
UNCLASSIFIED
UNCLASSIFIED
ITNE Concept of Operations
(CONOPS) - Definition
Radio Platforms NetOps Management
The Radio Platform component is a combination System
of the hardware design inherent to the radio to The NMS component of the ITNE is the
include: antenna, batteries, IO Device, vehicular, integrated capability that allows network
man-pack or base mounts and the software managers to plan, configure, manage and
design inherent in the radio operating system. monitor all other components of the ITNE. This
The radio operating environment software allows includes radio platforms, mission command
the interaction between the radio hardware mobile/mounted applications, ancillary devices,
components and the NetOps and Waveform and waveform applications. The NMS is the
Applications component software. In the legacy capability through which the Battalion S-6 staff
radios, the hardware and software design are fully develops and builds a network plan and
integrated within the radio and include the initializes and operates the radio network for
waveform their respective command level.
Battalion WNW Within the ITNE, there are two terrestrial based tiers; a
... celestial based tiered focused on a narrowband satellite
... communications (SATCOM) capability; and potentially an
... Company SINGARS ...
Lower Tier
objective aerial layer tier. The aerial tier is not available
Platoon SRW Platoon SRW in near term capability sets (CS 13/14) but may be added
Platoon SRW Platoon SRW Mid Tier in later capability sets as required.
Company WNW
The terrestrial based tier is divided into a lower and a
mid tier. These tiers are mutually supportive and are
both required in order to provide a robust radio based
Figure does not depict the narrowband SATCOM interoperability points within the Lower and Mid tier terrestrial layer for organic passage of voice and data for
ITNE nor the celestial, aerial, and terrestrial connectivity points with higher headquarter elements. tactical edge commanders.
Lower Tier: The lower tier portion of the ITNE is composed of organic Mid Tier: The mid tier portion of the ITNE is composed of organic network
network resources from each ITNE functional component designed to support resources from each ITNE functional component designed to support battalion
company and below formations down to soldier. This tier is characterized by and company level operations. The mid tier is the critical high capacity
primarily single channel radios operating at both the unclassified and secret backbone of the radio environment. It provides the battalion and company
level along with two channel radios at platoon and company to ensure multi- commander with the means to process voice and larger amounts of data
network integration and connectivity. The provisioning of mission command across their tactical formation over a terrestrial based network. In addition, the
information is provided by mobile applications that enable visualization, and mid tier is the interoperability point for higher echelons, Joint integration,
human machine interface and ancillary devices such as GPS receivers that aviation integration, and multinational interoperability. The primary mid tier
provide Position, Navigation, and Timing (PNT) information for basic soldier waveform is the Wideband Networking Waveform (WNW). There is the
and unit situational awareness (SA), fires targeting data, voice, and sensor potential that other mid tier waveforms could be added and/or combined as
capability. The primary lower tier waveforms are the Soldier Radio Waveform the ITNE evolves over time. These waveforms are defined in Appendix F.
(SRW) and SINCGARS. There is the potential that other lower tier waveforms Figure 2.0 below illustrates the objective relationship between the lower and
could be added and/or combined as the ITNE evolves over time. mid tier portions of the ITNE. The objective ITNE requires a robust mid tier
capability within the company and the battalion.
UNCLASSIFIED
UNCLASSIFIED
ITNE Concept of Operations
(CONOPS) – S-6 Functions
UNCLASSIFIED
UNCLASSIFIED
ITNE Concept of Operations
(CONOPS) – Planning Process
Multiple Phases The ITNE Signal Operations Planning
Process is the most crucial phase for the S-
6 staff.
The Planning Process of ITNE Signal Operations involves five phases that cover all activity If the plan is wrong from inception, the
required by the S-6 staff. This includes everything from the receipt of their commander’s Management and Analysis Processes of
operations order to the verification that the commander’s network is initialized and fully ITNE Signal Operations are likely to fail.
operational. The five Planning Process phases include the Signal Analysis Phase, the Data
The ITNE cannot be initialized and made
Collection Phase, the Network Design Phase, the Network Build Phase, and the Network
Load/Verification Phase. In total, these five phases include thirty separate steps that must be
operational with a plan that is fundamentally
performed to standard by the appropriately trained soldier skill set. Failure to follow the steps flawed in either concept or design.
correctly can easily result in planning mistakes that create capability gaps in the network
design and/or flawed ITNE data synchronization across all devices. Minimally, these failures
will result in certain incorrectly planned devices from initializing. In extreme cases, the entire
ITNE can fail to initialize.
UNCLASSIFIED
UNCLASSIFIED
ITNE Concept of Operations
(CONOPS) – Management Process
Multiple Phases
The Management Process within ITNE Signal
Operations provides the S-6 staff with the means to
monitor and affect ITNE component systems in real
time. This requires an ability of each ITNE system
to advertise key information elements to the ITNE
NMS and for the ITNE NMS to collect those
information elements, analyze them, and provide an
overall status with regard to the information
category collected.
UNCLASSIFIED
UNCLASSIFIED
ITNE Concept of Operations
(CONOPS) – Analysis Process
Single Phase (Cyclic) The Analysis Phase of ITNE signal operations
provides the S-6 staff the ability to review, refine,
adapt, and improve upon all aspects of ITNE
signal operations.
The Analysis Process of ITNE Signal Operations involves four steps that As with the previous phases of ITNE signal
operations, the Analysis Phase in the near term
leverage the information and data collected during the Planning and Management
(CS 13/14) is a completely manual process. The
Processes. The Analysis Process begins at any point but for purposes of
mechanism for tracking and recording must be
illustration is shown in this CONOPS as a third process because it leverages the
done with home grown tool sets like PowerPoint,
data collected in the first two processes of ITNE Signal Operations. Analysis is Excel, and/or Word. In the mid to long term (CS
always ongoing and there is no limitation to conducting the Analysis Process 15 and beyond), the ITNE NMS will incorporate
concurrently with the Planning or Management Processes so long as the S-6 has automated system capabilities that allow for the
the staff, time, and the data is relevant within the context of the mission planning replay of key features within a previously run
cycle. The four steps of the Analysis Process include Identify Trend Analysis mission command network and identify areas for
Report (TAR), Generate TAR, Analyze TAR, and Record Lesson Learned. further analysis and improvement.
UNCLASSIFIED
UNCLASSIFIED
ITNE Planning Process
(Signal Analysis Phase)
Art of War
Commander’s Intent to Signal Estimate
The Signal Analysis Phase is the first phase of the ITNE Planning Process and
begins with the receipt of the commander’s approved mission course of action to
include the approved task organization. The S-6 staff then analyzes the mission
command requirements and translates them into the Signal Estimate. The S-6 uses
the mission variables of Mission, Enemy, Troops, Terrain, Time, and Civilians
(METT-TC) to identify specified tasks, implied tasks, network constraints, assets
available, and commander support requirements in order to develop the Signal
Support Architecture (SSA) and the Radio Platform Preset Architecture (RPPA) for
ITNE. The Signal Estimate published at the completion of this phase contains the
SSA and the RPPA. There are six steps in the Signal Analysis Phase.
Signal Products: Information Flow Diagram, Network Plan (SSA, RPPA), Signal Estimate
UNCLASSIFIED
UNCLASSIFIED
ITNE Concept of Operations
(CONOPS) – Ontology Crosswalk
UNCLASSIFIED
UNCLASSIFIED
ITNE Planning Process
(Data Collection Phase)
Art of War
Network Plan to Data Correlation
The Data Collection Phase is the second phase of the ITNE Planning
Process and begins with the publication and availability of the
approved Signal Estimate and is completed when the S-6 receives all
requested data associated with the Signal Estimate required to build
the detailed unit network design. There are eight steps in the Data
Collection Phase.
Signal Products: Spectrum Range, COMSEC Key, IP Address Space, and Map Data
UNCLASSIFIED
UNCLASSIFIED
ITNE Planning Process
(Network Design Phase)
Art of War
Correlated Data to Network Design
The Network Design Phase is the third phase of the ITNE Planning Process and begins
once all the requested network data is received and the impact to any request denials
are fully vetted and approved by the commander and published in a final Signal
Estimate. Using the received ITNE data, the Battalion S-6 formulates an IP scheme
and a Network Routing Architecture (NRA). The Battalion S-6 then finalizes the SSA
and the RPPA by applying the IP scheme, network routing architecture, frequencies,
narrowband SATCOM, and COMSEC data. The completion of this phase is a published
Signal Annex to the battalion operations order that establishes the ITNE Network
Design (ND). There are six steps in the Network Design Phase.
UNCLASSIFIED
UNCLASSIFIED
ITNE Planning Process
(Network Build Phase)
Science of War
Network Design to Mission Command File
The Network Build Phase is the fourth phase of the ITNE Planning Process. In this phase, the
S-6 uses the Network Design from the previous phase and builds the Radio Network
Configuration File (RNCF) and Application Configuration File (ACF). With the completion of
these two products, the Battalion S-6 now has the ITNE Mission Configuration File (MCF). The
MCF includes all network device and application configuration files required to implement and
execute the battalion’s mission network. In the near term (CS 13/14), the Battalion S-6 then
manually tests and validates the MCF through direct access and observation. In the mid to
long term (CS 15 and beyond), the S-6 utilizes simulation tools built into the ITNE NMS. The
end state of this phase is the manual and/or automated distribution of the MCF to all battalion
units in support of follow-on Network Load/Verification Phase operations. The completion of
this phase is a published MCF. There are five steps in the Network Design Phase.
UNCLASSIFIED
UNCLASSIFIED
ITNE Planning Process
(Network Load & Verification Phase)
Science of War
Mission Command File to Verified Operational Network
The Network Load & Verification Phase is the fifth and last phase of
the ITNE Planning Process. In this phase, the S-6 and subordinate
units load all mission network devices and mission command
systems with their specific MCF, initialize the network, and conduct
a communications check. At the end of this phase, the S-6 provides
a commander approved operational network (OPNET) that meets
and supports the identified information exchange requirements.
There are four steps in the Network Load & Verification Phase.
UNCLASSIFIED
UNCLASSIFIED
ITNE Management Process
(Verify OPNET)
Science of War
Mission Command File to Verified Operational Network
The Verify OPNET portion of the ITNE Management Process begins with Step 30 of
the ITNE Planning Process when the Network Load/Verification Phase is completed
through the communications check process and ends when the S-6 validates that the
MCF meets the information flow requirements of the commander established in the
Signal Analysis Phase of the ITNE Planning Process. This is accomplished by
comparing the DSSA and the DNS to the actual NCOP populated in the Verify
OPNET process. Once the NCOP and DSSA and DNS are validated, the MCF is
valid and the ITNE is fully initialized and ready for mission command operations.
There are three steps in the Verify OPNET process.
UNCLASSIFIED
UNCLASSIFIED
ITNE Management Process
(Fault Management)
Science of War
Fault Detection to Fault Resolution
The Fault Management Phase provides for the detection, isolation and
resolution of network problems. The S-6 utilizes the Fault Management Phase
as an active listening capability on all ITNE networked devices. This capability
is configurable based on parameters established through the S-6. These
parameters are based on the commander’s primary concerns which once
again link to the information flow diagram developed early in the ITNE Planning
Process. The S-6 will focus monitoring on interoperability nodes, crossbanding
locations, Battalion interconnectivity, communication with higher and attached
units, and quality of service performance. There are six steps in the Fault
Management Phase.
UNCLASSIFIED
UNCLASSIFIED
ITNE Management Process
(Administrative Management)
Science of War
Administrative Change Management
The Administrative Management Phase of the ITNE Management Process includes those
functions that add, change, modify, delete, and/or update administrative information within
the MCF. The cause for these administrative changes are as simple as adding a new soldier
or as complex as executing a unit task reorganization (UTR). Administrative Management
includes. but is not limited, to some of the following common functions: management of
authorized users by establishing names, passwords, roles, and permissions with a user
based login policy; performing systems software backup, updates, and synchronization; and
executing UTRs. In the near term (CS 13/14), functions within the Administrative
Management Phase are performed across a range of systems by different soldiers within the
BCT S-6 and Battalion S-6. In the mid to long term (CS 15 and beyond), the BCT and
Battalion S-6 will utilize the ITNE NMS to manage all of these functions within their
respective echelons organic and attached network. There are six steps in the Administrative
Management Phase.
Signal Products: Component Updates, Preset Changes, Trend Analysis Reports
UNCLASSIFIED
UNCLASSIFIED
ITNE Management Process
(Performance Management)
Science of War
Network Performance Monitoring & Control
The Security Management Phase of the ITNE Management Process involves all
activities that the S-6 undertakes to protect ITNE component device value,
usability, data integrity, and continuity of operations. The staff must effectively
identify threats and then choose the most effective ITNE NMS tool to combat
them. In the near term (CS 1/14), ITNE Security Management is limited to
communications security (COMSEC) protections and local account login
procedures. In the mid to long term (CS 15 and beyond), the ITNE NMS will
provide security services that include host based and external intrusion protection
and prevention capabilities. The Security Management Phase is an extension of
the Fault and Performance Management Phases for security devices within the
ITNE components. There are four steps in the Security Management Phase.
ITNE CONOPS
Unit Task Reorganization (UTR)
(Appendix K)
29 UNCLASSIFIED
UNCLASSIFIED
UTR Challenges
• Since the initial fielding of these ITNE systems in fiscal year 2012, the
Army, through the Assistant Secretary of the Army for Acquisition,
Logistics, and Technology (ASA(ALT)), provided supporting contract
personnel to assist in all facets of planning and management of the
ITNE
• ITNE Signal Operations as defined in this CONOPS is primarily
performed by a number of ASA(ALT) program managers,
organizations, and contractors. The only portion performed by
soldiers to date is the Network Build Phase and the Network
Load/Verification Phase of the ITNE Planning Process
• The first three phases are currently executed by ASA(ALT). Until units
are able to properly execute all the steps of the ITNE Planning
Process, they will run a high risk of properly managing their network
once operational if there are any issues related to the SSA, RPPA, NP,
and ND
• These products and their associated predecessor steps must be
owned and performed by the S-6 in order for the responsible
commander to truly control their tactical network
30 UNCLASSIFIED
UNCLASSIFIED
UTR Definition
31 UNCLASSIFIED
UNCLASSIFIED UTR Process
(Slide 1 of 2)
• During the ITNE Planning Process for a UTR, it is imperative that the S-6 quickly
gauge their ability to execute the UTR within a certain period of time. This is to
ensure the S-6 can provide a risk assessment to their commander on the likelihood of
UTR success given the time provided. Where the time frames will not meet the
execution of a UTR to standard, the S-6 must quickly notify the commander and
provide alternative approaches by trading capability to ensure some measure of
network connectivity and services.
• The connectivity and services chosen for the time frame involved should meet the
commander’s information priorities noted in the Signal Analysis Phase of the ITNE
Planning Process. Notification of UTR time requirements must be given to the
command and staff in the early stages of the ITNE Planning Process. This must
occur as soon after receiving the approved task organization as possible.
• The commander will always set information flow priorities on the network. However,
until that direction is provided, the S-6 should always start their prioritization of
communications and network capability based on the establishment of the transport
and networking components of the ITNE before the mission command application
capability. The following is a high level list of capability priorities during ITNE UTR
planning and execution operations.
32 UNCLASSIFIED
UNCLASSIFIED UTR Process
(Slide 2 of 2)
Capability Priorities:
• Priority 1: Local Transport: (Radio Platforms: SINCGARS, SRW, and Mid Tier
waveforms)
• Priority 2: Mission Command Applications (JBC-P, Nett Warrior) capable of running
on the local transport only.
• Priority 3: Wide Area Transport (Ancillary Devices: Tier III routers, cross domain
solutions, and gateways) to link together the local transport.
• Priority 4: Mission Command Applications (JBC-P, Nett Warrior) to run data services
across the wide are transport.
• Note: Voice capability is always the first priority over mission command data.
33 UNCLASSIFIED
UNCLASSIFIED
UTR Types
• Planned UTRs: The planned UTR is instantaneous upon execution as a preset on a radio
platform or networked ancillary device. The time involved in executing the ITNE Planning Process
for a pre-planned UTR is done before mission time and is therefore inconsequential to the S-6 and
their staff during mission operations. However, the need to follow the ITNE Planning Process
from beginning to end is essential to ensure the pre-planned network is functional and meets all of
the pre-planned UTR task organization information flow requirements. Failure to ensure this
before loading that pre-planned UTR for a mission could cause an unforeseen failure during
mission operations and result in catastrophic loss of communications and network capability.
• Unplanned UTRs: The unplanned UTR is much more difficult due to the need to execute the
ITNE Planning Process and Verify OPNET process during mission time. In order to properly
handle the risk associated with the time requirements for unplanned UTRs, the S-6 must be able
to conduct a quick estimate on the time required to complete the ITNE Planning Process and
Verify OPNET process for their commander in order to ensure there is sufficient time to execute
the task organization specified. An inability to estimate the UTR time during the Signal Analysis
Phase could result in a failure to complete the ITNE Planning Process and Verify OPNET Process
in time for mission execution thus jeopardizing the entire mission and command.
• Risk Mitigation: The S-6 mitigates the risk associated with UTR time estimation and mission
execution time requirements by determining the level of complexity for the particular UTR as a
measure of soldier tasks required. This is a subjective assessment to help the S-6 organize their
staff. Secondly, the S-6 actually calculates an estimated time factor based on a formula designed
to equate system ITNE Planning Process and Verify OPNET time with UTR time. The UTR
categories of complexity are noted in Table K1 of the ITNE CONOPS. The UTR completion time
calculation is discussed in paragraph 4.2 of that appendix.
34 UNCLASSIFIED
UNCLASSIFIED UTR Process
(Complexity Categorization)
Organizational Modification: This UTR Network Tiers: This UTR complexity factor
complexity factor measures the relative measures the relative complexity of the volume of
complexity of the task organization structure network systems based on the number of required
deviation from the unit’s specific MTOE. network tiers affected by the UTR.
Network Levels: This UTR complexity factor measures the relative
complexity of the interconnectivity planning required between the Upper
Tactical Internet (UTI) network and systems and the ITNE network and
systems based on the amount of interconnection and crossbanding points
required for the particular UTR.
35 UNCLASSIFIED
UNCLASSIFIED UTR Process
(Network Planning Times)
36 UNCLASSIFIED
UNCLASSIFIED UTR Process
(Time Completion Calculation)
• UTR Completion Time Calculation: The S-6 and their staff can
quickly estimate the amount of time it takes to plan, configure, load,
initialize, and validate a set of networks to match a UTR by applying
the following formula.
𝑛
𝑇𝑈𝑇𝑅 = 𝑋𝑖𝑇𝑖𝑁𝐸𝑇
𝑖=1
37 UNCLASSIFIED
UNCLASSIFIED UTR Process
(Planning Considerations – Slide 1 of 2)
• UTR NPs, NDs, and MCFs can be planned and loaded as a preset on ITNE
component devices expected to utilize that network design for a particular
set of missions. These UTRs range across all categories listed under
paragraph 4.0 of the ITNE CONOPS and are only limited to the imagination
of the commander and their staff in preparing for contingencies.
38 UNCLASSIFIED
UNCLASSIFIED UTR Process
(Planning Considerations – Slide 2 of 2)
• Preset space is a precious resource for the S-6. There is always a need to
use a percentage of preset space for high probability task organization
scenarios. In effect, these should be baked in doctrinal presets for the
movement or pure fleeted units as discussed earlier in this appendix.
However, there is also a need for each unit to develop their own planned
task organizations that go beyond pure fleeted organizational movements
and include more CAT1 and CAT 2 A/B type organizational structures to
meet their unique mission requirements. A good S-6 always leaves room
on a radio for these kinds of mission specific pre-planned presets.
• In the near term (CS 13/14), the S-6 will receive their preset design, the
RPPA, from their ASA (ALT) new equipment fielding (NEF) process. This
baseline is formed on the latest considerations between the unit and the
ASA (ALT) network design developers to facilitate the mission specific and
doctrinal level requirements for planned missions. Over time, this
responsibility will migrate directly to the unit rather than the program
managers. Once this occurs, the unit will have the responsibility and control
over the design of their RPPA in the Signal Analysis Phase of the ITNE
Planning Process.
39 UNCLASSIFIED
UNCLASSIFIED
ITNE
Dependencies
UNCLASSIFIED
UNCLASSIFIED
ITNE Dependencies
(Spectrum)
CS 15 and Beyond Objective Radio Basis of Issue
•IBCT:
IBCT •PRC-154 (Rifleman Radio)
•PRC-154A (Nett Warrior Radio)
•PRC-155 MP dismounted/mounted)
•SRW Appliqué
CS 12 and Earlier Legacy Radio • MNVR
Basis of Issue • VRC-87 thru 92
•PRC-150 & VRC-104(V)3
•VRC-87 thru 92 SINCGARS •VRC-148
•PRC-150 & VRC-104(V)3 •PSC-5 & PRC-117F
•VRC-148
•PSC-5 & PRC-117F & VRC-103
SATCOM Approximately:
•PRC-117F 3,500 Total Radios in Objective IBCT
•LMR
Approximately:
1,500 Total Radios in Legacy IBCT
Terrestrial Logical
Network
(Voice) Current Blue SA data is controlled
and configured by the Army
Local IP Addressing Enterprise through ASA(ALT)
programs PD TNI and PD FBCB2
Unit ownership of
ITNE component
data is critical to
organic task
reorganization
42 UNCLASSIFIED
UNCLASSIFIED
ITNE Dependencies
(Data Product Process & Staging)
43 UNCLASSIFIED
UNCLASSIFIED
ITNE Dependencies
(Personnel Resourcing)
• VICTORY Architecture
• Spectrum capability at battalion
• Unknowns
44 UNCLASSIFIED
UNCLASSIFIED
ITNE
Troop to Task List
45 UNCLASSIFIED
UNCLASSIFIED
Leadership Operator
(31 Draft High Level Tasks) (147 Draft Tasks)
STEP Task Task Description MOS
The Signal Support Architecture (SSA) is populated with the support of all members of the battalion S6, but the ultimate
1 DSSA responsibility lies with the Battalion S6 OIC and the Battalion S6 NCOIC to review the SSA will support the network common 25A, 25U
operational picture (NCOP)
The Battalion S6 will discover network specifics (DNS) by visualizing and monitoring detailed data associated with each
2 DNS Network INTE device populated in the DSSA/NCOP. The DNS completes the overall NCOP when combined with the DSSA 25A, 25U, 25B
and allows the S6 to check on key network functionalities.
MCF validation is required by the S6 to compare the DSSA and DNS against the NP and ND. When MCF is validated the S6
3 Validate MCF monitoring mission will then begin with the ITNE management process. 25A, 25U, 25B
Fault Management Phase provides for detection, isolation and resolution of network problems for all ITNE networked
F Fault Management Phase components.
This step is designed to monitor the ITNE component systems based on METT-TC priorities and identify when a fault has
F1 Detect Fault occurred 25U, 25B
Once the fault has been detected Battalion S6 is then responsible to isolate the fault by reviewing event logs, network
F2 Isolate Fault analysis and any other network activity information. 25A,25U, 25B,25Q
After battalion S6 Isolates the fault, the section is then responsible to identify the fault and the reason for the fault (e.g. fault
F3 Fault Diagnostic size, location and time of detections). 25A,25U, 25B,25Q
Once Network data is collected in relation to the fault with the isolation of the fault the battalion S6 is responsible to then be
F4 Identify Root Cause able to make a reasonable estimation of the faults primary cause. 25A,25U, 25B,25Q
The battalion S6 is responsible to focus on the positive and negative consequences of particular faults and determine the
F5 Determine Solution course of action depending on the severity of the fault. 25A,25U, 25B,25Q
During operations, the Battalion S6 is responsible to assess fault trends that occur on a daily basis to help combat future
F6 Trend Analysis/Archiving faults. 25A,25U, 25B,25Q
At their present time of unit operations the Battalion S6 is responsible to use the correct remedy to address the fault at that
F7 Execute Restoration time. 25A,25U, 25B,25Q
This phase includes functions that add, change, modify, delete, and/or update administrative information within the MCF.
A Administrative Management Phase
Battalion S6 is responsible to ensure all ITNE network components receive the required updates (hardware and/or
A-1 Component Updates software) periodically, which is necessary to keep the ITNE components protected from vulnerabilities. 25U, 25B, 25Q
Battalion S6 is responsible to ensure the signals assets across the network is distributed appropriately to support combat
A-2 Asset Distribution operations. 25A,25U
The battalion S6 accounts for each role name and associates them with each respective radio platform
A-3 Role Name Modification 25B,25U
The battalion S6 is responsible to assist key battalion staff leaders to execute a preset change for all associated ITNE
A-4 Radio Platform Preset Change Over network components to ensure the components are ready for a specific mission. 25A
The battalion S6 is responsible to track performance data on all ITNE network components with data collected during each
A-5 Trend Analysis/Archiving specific combat operation conducted. 25A,25U, 25B,25Q
Battalion S6 measure and optimize the ITNE network to ensure the commanders priorities are supported.
P Performance Management Phase 25A,25U
Battalion S6 is responsible to track all ITNE network components using the ITNE NMS. Parameters monitored will be
P-1 Monitor Parameters filterable data collection polling, automated analysis of preset formulas, performance thresholds, and reporting capabilities. 25U,25B,25Q
Once performance metrics have been review, Battalion S6 personnel is responsible to correlate all relevant data and
P-2.1 Conduct Diagnostic determine the reason for failures/defiencies. 25A,25U,25B,25Q
The battalion S6 is responsible to track performance data on all ITNE network components with data collected during each
P-3 Trend Analysis/Archiving specific combat operation conducted. 25A,25U,25B,25Q
Battalion S6 is responsible to automatically change and/or modify performance setting on any ITNE component device.
P-4 Execute Performance Changes 25A,25U,25B,25Q
Battalion S6 is responsible to implace security measures to protect all ITNE components by identifying threats and choosing
S Security Management Phase the most effective NMS tool to combat them. 25B,25U
Battalion S6 is responsible to monitor all security parameters to protect all ITNE network components using the ITNE NMS.
S-1 Monitor Parameters Parameters monitored will be filterable data collection polling, automated analysis of preset formulas, performance 25B,25U
thresholds, and reporting capabilities.
Battalion S6 personnel is responsible to review all available security related performance metrics, correlate all relevant data
S-2 Conduct Diagnostic and determine the reason for failures/defiencies. 25B,25U
Battalion S6 is responsible to conduct performance tests for cross domain solution settings, Host Based Security Systems
S-2.1 Conduct Diagnostic (HBSS) Configurations, and other device performance settings. 25B,25U
Battalion S6 staff is tasked to track variances and or efficiencies regarding ITNE component security device performance.
S-3 Trend Analysis/Archiving 25B,25U
Additional task within this step the Battalion S6 will combine the collected performance data accrossed a specified period to
S-3.1 Trend Analysis/Archiving aid the S6 staff to determine the asset utilization methodologies. 25B,25U
Battalion S6 staff is tasked to execute security changes by automatically changing and/or modifying performance settings
S-4 Execute Security Changes on all ITNE components requiring security parameter updates 25B,25U
The troop to task list effort incorporates lessons learned from Network Integration Exercises,
Operational Needs Statement and Capability Set Fieldings, and experimentation and critical
analysis from the user community.
UNCLASSIFIED
UNCLASSIFIED
Signal Center of Excellence
Key Points of Contact
UNCLASSIFIED
UNCLASSIFIED
Questions
UNCLASSIFIED