Joint Interface Control Officer (JICO) Support System (JSS)

1
Joint Interface Control Officer (JICO) Support
System (JSS)
CDR Matt Kercher USAF TDL System Program
Office Hanscom AFB, Massachusetts, USA
2
JSS Program Fundamentals

• US Joint Requirements Oversight Council approved
  the JSS Operational Requirements Document (ORD)
  on 15 July 2002
• Approved 12 system key performance parameters
• Designated a Joint Program led by Air Force
• Air Force was assigned ORD responsibility

3
JSS Key Performance Parameters

• (Information Exchange) Interoperability
• Message Set Interoperability
• Communications Interoperability
• Training
• Automated access to search driven information
• Information Integrity
• Quality of Service
• Transport Element Status
• Data Interoperability
• Network Management
• Information Assurance Defense
• Survival Information Dissemination

Derived from Theater Air and Missile
Defense Capstone Requirements Document
4
JSS Development Strategy
The JSS program shall adhere to the spiral
development process. Quick and efficient
implementation of the selected approach is key to
successful execution of each increment within the
goal of 18 months or less. -- JSS ORD
FY04 FY05 FY06 FY07 FY08 FY09
Program Start
S/W Drop
Notional Schedule
S/W Drop
5
Development Strategy

• Phased Approach
• Navy and Air Force are funding Phase I
• Phase I is outlined in a Memorandum of Agreement
• Phase I goals are to field priority capabilities
• Phase II will bring in full participation of Army
  andMarine Corps

6
Schedule

• JSS will be an evolutionary acquisition program
  designed to extract, improve upon, and condense
  required capabilities (forwarding, translation
  and data management with a distinct presence)
  from existing technology
• IOC will be achieved when the following
  conditions are met
• One JSS set supporting an ashore OPFAC and one
  set supporting an afloat OPFAC in accordance with
  the Operations Concept
• Remote Joint Data Repository is operational and
  maintainer/administrator is available
• JSS training course has been established, to
  include operator and maintenance training
• Initial Joint Interface Control Cell team per
  service has been trained
• All program documentation, including acquisition,
  operator and maintenance documentation, is
  baselined, formally controlled, and approved
• Maintenance support is established
• All key performance parameters have been met

7
Schedule

• Initial Operational Capability is currently
  planned for fiscal year (FY) 2006 (Objective), FY
  2007 (Threshold)
• Full Operational Capability (FOC) shall be
  achieved when the following conditions are met
• All four Joint Forces Command specified FEC sets
  are delivered in addition to meeting IOC criteria
• JSS is also available at JICC-D (2) and JMTS (2)
• JSS is installed in at least one (1) OPFAC per
  Service
• Remote JDR will support both configurations
  simultaneously at IOC locations
• JSS training site (expected to be FORSCOM) has
  access to the remote JDR for training purposes
• FOC is currently planned for FY2008 (O) FY 2009
  (T)

8
JSS System Capabilities

• Spectrum Supportability
• JICO Data Repository (JDR)
• Database Management
• Information Display
• Processing Latency
• Operating Power
• Automatic Alerts
• Dynamic Reconfiguration
• Deployment Response and Removal Time
• Physical and Operational Security Needs
• Mission Capabilities
• C4I Standard, Interoperability, and Commonality
• Transmission Security

• JSS Interface Control
• Restart and Recovery
• Work Station
• Automation and Information Dissemination
  Management (IDM) Support
• JICO Management
• Planning
• Training
• Data Analysis
• System Performance
• Information Exchange Requirements
• Sustainment
• Voice, Data, and Video Fusion

9
JSS Configurations

• The Operational Requirements Document describes
  the JSS as 2 adaptive capability packages
• Common Core Capability
• in which the operational facilitys (OPFAC)
  communications systems are used to the maximum
  extent possible and will include only that
  hardware, software, and communications interfaces
  necessary to meet the requirements in the ORD
• Full Expeditionary Capability
• a deployable, self-contained system
• The JSS (CCC) in a ruggedized, transportable
  configuration with all associated communications
  equipment required to support JICO operations
  (data and voice). JSS (FEC) is ideal for a
  combatant command or Service requiring a rapidly
  deployable JICO capability able to set up and
  operate in immature or austere environments.

10
Short History of JICO Systems in US

• Navy Common Data Link Management System (CDLMS)
• Joint Interface Control Cell Deployable
  (JICC-D)
• Interim JICO Support System (I-JSS)

11
Navy CDLMS

• Integration of Link-11 data terminal set, C2P
  computer program (C2P rehost), and operator
  controls (HMI) in a consolidated cabinet
• Link monitoring was limited to Link 11
• Upgrade path was envisioned for Link 16, but
  never pursued
• Only available on Navy Model 5 ships

12
Current C2P Rehost/CDLMS Model 5Multi-TADIL
Block Diagram
AN/UYQ-86(V)2 CDLMS
Secure Voice (2) (Analog w/control discretes)
L- Band
OJ-746(V)/UYQ HMI Work Station
OL-649(V)/UYQ MDU (Keyboard/Monitor/Printer)
OJ-742(P)/UYQ ESPG (AN/UYQ-70(V))
RGB Video
FDDI
CDLMS Subsystem
KG-84 SATCOM (S-TADIL J)
Ethernet Printer
MIL-STD 1397C Type F
SATCOM
2/
PS/2 Kybd/Trk Ball
RS-232/449
C2P (R)
USQ-118 Link-4A
2/
ACDS Blk 1 Level 2.1X
UHF
MIL-STD 1397C Type E
MIL-STD 1397C Type E
MIL-STD 1397C Type A
KG-40 (2)
MIL-STD 1397C Type A
OL-650(V)/UYQ CSDTS Link-11
4 /
HF/UHF LOS UHF SATCOM
MIL-STD 188-203-1 (Audio)
PMW 159 cog equip

MIL-STD 188-114 (Digital)
LEGEND
13
JICC-D

• US Forces Command initiative to provide a link
  monitoring and situational awareness tool for
  JICOs
• No development, integration only
• Systems (evolutionary build)
• Air Defense Systems Integrator (APC)
• iMTDS (MITRE)
• Joint Range Extension Gateway (Titan)
• LMS-16 later upgraded to LMS-MT (Northrop
  Grumman)
• Communications equipment (JTIDS Class 2, USQ-125,
  voice)

14
Interim JICO Support System

• An Air Force initiative to procure a
  non-developmental Link-16 monitoring system for
  Air Force operational forces.
• Electronic Systems Center (Hanscom AFB)
  contracted for 15 systems from Northrop Grumman
  Information Technologies in 2002
• All systems have been delivered and fielded
• Navy collaborated with Air Force for 3 systems
  used as components of a carrier-based prototype
  (Link Monitoring Capability)
• I-JSS is an independent project from JSS
  development
• Considered a prototype capability used for
  evaluating and investigating link monitoring
  requirements

15
I-JSS Notional System Layout
ViaSat AN/GRR-43(C)
1553
Antenna
Ethernet
Advanced Programming Concepts ADSI
Land Line
Northrop Grumman LMS-MT
Modem
TADIL B
RED LAN
KG-84
KG-84
KG-84
1553
TADIL J
JTIDS
Multi-TADIL Data
TADIL A
NTDS-A
Link-11 Radio
KG-40A
16
Lessons from prototypes for JSS

• JICO requires multi-link integrated tool suite
• Tools for network planning are quite limited, and
  this is the JICOs most desired tool
• JICOs role is expanding (e.g., track management,
  gateway manager) which are not adequately
  captured in the requirement
• Concept of operations and employment for JSS is
  urgently needed to address how the system will be
  used and operated in joint and multi-national
  task forces
• Remote management of devices (gateways, hosts,
  terminals) is desired, but no clear direction
  exists
• JTRS equipment will greatly elevate JSS required
  capability

17
Acronyms

• C2P Command and Control Processor
• CDLMS Common Data Link Management System
• JICO Joint Interface Control Officer
• JICC-D Joint Interface Control Cell, Deployable
• JSS JICO Support System
• I-JSS Interim JICO Support System
• IOC Interim Operational Capability
• iMTDS Improved Multi-TDL Display System
• LMS Link Monitoring System
• OPFAC Operational Facility
• FOC Full Operational Capability
• JDR Joint Data Repository
• LMC Link Monitoring Capability