02.03.2015 Views

JP 3-01 Countering Air and Missile Threats - Defense Innovation ...

JP 3-01 Countering Air and Missile Threats - Defense Innovation ...

JP 3-01 Countering Air and Missile Threats - Defense Innovation ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter II<br />

(6) Joint Interface Control Officer (JICO). The JICO is the senior interface<br />

control officer in support of MTN operations <strong>and</strong> is the MTN coordinator for the JDN within<br />

the theater/JOA. The MTN is the primary feed/data source to support generation of a CTP.<br />

The CTP subsequently feeds the CCDR’s theater COP. The JICO is responsible for<br />

planning, monitoring, <strong>and</strong> managing the architecture <strong>and</strong> technical integration of joint data<br />

<strong>and</strong> communications systems for the MTN. The MTN components are the TDLs such as<br />

Link 11, Link 11B, Link 16, etc. The JICO controls <strong>and</strong> acts as the coordinating authority<br />

for the joint interface control cell (JICC) <strong>and</strong> for any regional interface control officer<br />

(RICO)/sector interface control officer (SICO) for planning <strong>and</strong> executing TDL functions<br />

that cross regional <strong>and</strong>/or sector boundaries or impact the theater-wide MTN. When a JTF is<br />

formed, there will be only one JICO per JTF, <strong>and</strong> the JICO will normally be located in a C2<br />

facility with connectivity to the primary TDLs (normally the JAOC). There may be Service<br />

component interface control officers located at the JICC.<br />

(a) When regional/sector AD comm<strong>and</strong>s are established, the JICO will<br />

coordinate with the RICOs/SICOs designated for <strong>and</strong> normally located at those comm<strong>and</strong>s.<br />

The RICO/SICO coordinates with the JICO but is responsible to the RADC/SADC for TDL<br />

continuity at their level. RICOs/SICOs may require interface control cells depending upon<br />

the complexity of their TDL networks. See Figure II-2 for a depiction of a notional joint<br />

interface control officer functional/comm<strong>and</strong> relationship.<br />

(b) The JICO is responsible to the JDNO for the MTN, which is one of four<br />

networks in the JDN. In turn, the JDNO is responsible to the JFC for integration of<br />

information from the sub-networks into a common track database used to generate the CTP.<br />

The JDN is the primary feed to support generation of the CTP. The CTP <strong>and</strong> information<br />

from the joint planning network contributes to the COP.<br />

Refer to Chairman of the Joint Chiefs of Staff Manual (CJCSM) 3115.<strong>01</strong>B, Joint Data<br />

Network (JDN) Operations, <strong>and</strong> CJCSM 6120.<strong>01</strong>D, Joint Multi-Tactical Data Link (TDL)<br />

Operating Procedures, for full details regarding the JICO <strong>and</strong> JDN <strong>and</strong> TDL operations.<br />

(c) Navy interface control officer for IAMD located at the MOC (with JFMCC<br />

or CTF IAMD) also requires connectivity to the primary TDLs as both a redundant<br />

capability to the JAOC JICO <strong>and</strong> in support of C2 of multi-mission Navy IAMD forces or as<br />

a RADC/SADC.<br />

16. Situational Awareness<br />

“When we started our deployment, we had only the most rudimentary<br />

communications infrastructure in Southwest Asia <strong>and</strong> the challenge of distance<br />

was daunting. Thanks to good planning <strong>and</strong> our underst<strong>and</strong>ing of the<br />

importance of satellites, we quickly <strong>and</strong> smoothly transitioned to a mature<br />

tactical theater network.”<br />

General Colin L. Powell, United States Army,<br />

Chairman of the Joint Chiefs of Staff<br />

December 1990<br />

II-24 <strong>JP</strong> 3-<strong>01</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!