Upload
magdalene-campbell
View
255
Download
12
Embed Size (px)
Citation preview
1
USAF TDL SPO
Joint Interface Control Officer (Joint Interface Control Officer (JJICO) ICO) SSupport upport SSystem (JSS)ystem (JSS)
CDR Matt KercherUSAF TDL System Program OfficeHanscom AFB, Massachusetts, USA
2
USAF TDL SPO
JSS Program FundamentalsJSS 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
____________________________________________________________________________________________
JOINT INTERFACE CONTROL OFFICER (JICO) SUPPORT SYSTEM (JSS)
OPERATIONAL
REQUIREMENTS DOCUMENT (ORD)
ACAT III
Version 4.0
WILLIAM J. FALLON DANIEL P. LEAF, Maj Gen, USAF Admiral, U.S. Navy Director of Operational Requirements Vice Chief of Naval Operations DCS/Air & Space Operations OPR: CNO N62; HQ USAF/XORI Phone: Comm (703) 601-1434; Comm (703) 601-0153 ____________________________________________________________________________________________________________________________________________________________ Distribution:
____________________________________________________________________________________________
JOINT INTERFACE CONTROL OFFICER (JICO) SUPPORT SYSTEM (JSS)
OPERATIONAL
REQUIREMENTS DOCUMENT (ORD)
ACAT III
Version 4.0
WILLIAM J. FALLON DANIEL P. LEAF, Maj Gen, USAF Admiral, U.S. Navy Director of Operational Requirements Vice Chief of Naval Operations DCS/Air & Space Operations OPR: CNO N62; HQ USAF/XORI Phone: Comm (703) 601-1434; Comm (703) 601-0153 ____________________________________________________________________________________________________________________________________________________________ Distribution:
3
USAF TDL SPO
JSS Key Performance ParametersJSS 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 DisseminationD
eriv
ed f
rom
The
ater
Air
and
Mis
sile
Def
ense
Cap
sto
ne R
equi
rem
ents
D
ocum
ent
4
USAF TDL SPO
Notional ScheduleNotional Schedule
JSS Development StrategyJSS 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
Program Start
S/W Drop
S/W Drop
FY04 FY05 FY06 FY07 FY08 FY09 +
5
USAF TDL SPO
Development StrategyDevelopment 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 and
Marine Corps
6
USAF TDL SPO
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
USAF TDL SPO
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
USAF TDL SPO
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
USAF TDL SPO
JSS Configurations
• The Operational Requirements Document describes the JSS as 2 “adaptive capability packages”– Common Core Capability
“in which the operational facility’s (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
USAF TDL SPO
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
USAF TDL SPO
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
USAF TDL SPO
AN/UYQ-86(V)2AN/UYQ-86(V)2 CDLMSCDLMS
OJ-742(P)/UYQOJ-742(P)/UYQ
ESPG ESPG (AN/UYQ-70(V))(AN/UYQ-70(V))
L- BandSecure Voice (2)
(Analog w/control discretes)
USQ-118Link-4A UHF
CDLMS = Common Data Link Management SystemCSDTS = Common Shipboard Data Terminal Set (p/o CDLMS)C2P (R) = Command and Control Processor, RehostESPG = Embedded System Processor Group HMI = Human Machine Interface (p/o CDLMS)JTIDS = Joint Tactical Information Distribution System
MDU = Maintenance Display Unit (p/o CDLMS)S-TADIL J = Satellite Tactical Digital Information Link (TADIL) J
LEGEND:
KG-40 (2)
HF/UHF LOSUHF
SATCOMMIL-STD 188-114 (Digital)
SATCOM
OL-650(V)/UYQOL-650(V)/UYQ CSDTSCSDTSLink-11Link-11
ACDS Blk 1 Level 2.1X
MIL-STD 1397C Type E
2
/
4
/
2
/CC22PP(R)(R)
MIL-STD 188-203-1 (Audio)
MIL-STD 1397C Type E
CDLMSCDLMS SubsystemSubsystem
OL-649(V)/UYQOL-649(V)/UYQ MDUMDU(Keyboard/(Keyboard/
Monitor/Printer)Monitor/Printer)
OJ-746(V)/UYQOJ-746(V)/UYQ HMIHMIWork Work
StationStation
MIL-STD 1397C Type A
MIL-STD 1397C Type A
RGB Video Ethernet Printer
PS/2 Kybd/Trk Ball
FDDI
JTIDSJTIDSAN/URC-107(V)7AN/URC-107(V)7
LINK-16LINK-16
KG-84 SATCOM
(S-TADIL J)MIL-STD 1397C Type F
RS-232/449
PMW 159 cog equip=
Current C2P Rehost/CDLMS Model 5Multi-TADIL Block Diagram
13
USAF TDL SPO
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
USAF TDL SPO
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
USAF TDL SPO
Advanced Programming ConceptsADSI
Ethernet
Northrop GrummanLMS-MT
1553
Antenna
Link-11 Radio
RED LAN
TADIL A
TADIL B ModemLand Line
KG-84
JTIDS
KG-84KG-84
ViaSatAN/GRR-43(C)
I-JSS Notional System Layout
1553
NTDS-AMulti-TADIL Data
KG-40A
TADIL J
16
USAF TDL SPO
Lessons from prototypes for JSS
• JICO requires multi-link integrated tool suite• Tools for network planning are quite limited, and this is
the JICO’s most desired tool• JICO’s 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
USAF TDL SPO
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