1. Topic 11 Operational and Tactical Command and Control Systems
A. Introduction
The purpose of this topic is to introduce the student to operational and tactical command and control (C2) systems and their applications operating across the network infrastructure.
B. Enabling Objectives
11.1 DISCUSS the Global Command and Control System-Maritime (GCCS-M) and its role in Navy C2..
11.2 DISCUSS differences between GCCS-M 3.X and 4.X architectures.
11.3 DEFINE Common Operational Picture topologies, nodes, and Strike Group architectures.
11.4 DISCUSS use of Theater Battle Management Core System (TBMCS).
11.5 DISCUSS relevance of Automatic Identification System (AIS).
11.6 EXPLAIN the differences in capabilities of Link 4A, Link 11, and Link 16.
C. Topic Outline
1. Command and Control (C2)
2. Navy C2
3. COCOMs
4. JTF
5. C4I Systems
6. COP Topology and Nodes
7. GCCS-M
8. TWS
9. TBMCS
10. AIS
11. TDLs
Topic 11 Operational and Tactical
Command and Control Systems
Enabling Objectives
11.1 DISCUSS the Global Command and Control System-Maritime (GCCS-M) and its role in Navy C2..
11.2 DISCUSS differences between GCCS-M 3.X and 4.X architectures.
11.3 DEFINE Common Operational Picture topologies, nodes, and Strike Group architectures.
11.4 DISCUSS use of Theater Battle Management Core System (TBMCS).
11.5 DISCUSS relevance of Automatic Identification System (AIS) and its associated data flow.
11.6 EXPLAIN the differences in capabilities of Link 4A, Link 11, and Link 16.

2. Figure 11.1: Current and future C4I systems.
TTWCS
Figure 11.1: Current and future C4I systems.
C4I Systems
Naval C4I systems are the information systems, equipment, software, and infrastructure that enable the commander to exercise authority and direction over assigned forces (Figure 11.1). C4I systems also help the commander monitor and influence the actions of his/her forces through the chain of command. These systems support the following four basic functions:
Collecting. Gathering and formatting data for processing. Data could include: Track Data (e.g. Platform, Link, and ELINT tracks), Air Tasking Orders (ATO), and Mission Data Updates (MDU).
Processing. Filtering, correlating, fusing, evaluating, and displaying data to produce a Common Tactical Picture/Common Operational Picture (CTP/COP) required for commanders to take appropriate action.
Disseminating. Distributing data or execution information to appropriate locations for further processing or use.
Protecting. Guarding information from an adversary’s attempts to exploit, corrupt, or destroy it.
NECC
TWS
TDS

3. Tying it All Together: The COP
The central situational awareness display, spawning
detailed target cueing for targeting applications and
improving SA among warfighters
Link 11/16
Figure 11.2: Tying it all together – The COP.
Tying it all together: Common Operational Picture
Warfighters are faced with the challenge of making logical and sound strategic and tactical decisions. Today, more than ever, they have nearly unfettered access to real-time imagery, track information, and geopolitical developments, regardless of the source.
The management of the information is a significant hurdle that must be negotiated. In a Joint environment, the COP is essential for the gathering, processing, display, dissemination, and evaluation of tactical information.
A fused display of reconnaissance imagery from national assets, enhanced with surveillance video from UAVs, supported by timely and precise data from JSTARS and ELINT/SIGNINT/COMINT sensors, and disseminated via real-time data links ensures decision makers have access to the most relevant information in making tactical decisions and employing weapons systems to meet the threat.
C4I SYSTEMS

4. Common Operational Picture
Figure 11.3: The CCDR’s Common Operational Picture is a compilation of JTF CTPs.
Common Operation Picture (COP) Defined
The COP is the theater Combatant Commander’s (CCDR) view of the battle space. Simply stated, the COP is a compilation of the JTF component commander’s CTPs, JDN, and CIP (Figure 11.3). Baseline COP information may include:
Current position and associated movement data for hostile, neutral, and friendly, including interagency, forces of interest within a combatant commander’s AOR.
Overlays (e.g., boundaries, coordination measures), manual inputs, labels, etc., that show the commander’s intent, location of major headquarters, and environmental information.
Amplifying information essential for mission success (e.g. Air Tasking Order).
Common Intelligence Picture (CIP)
Simply stated, the CIP is the CTP updated with additional sources and methods. It is disseminated via the JWICS and displayed in a command’s Sensitive Compartmentalized Information Facility (SCIF) or Ship’s Signal Exploitation Space (SSES).

5. Figure 11.4: Notional COP theater.
CJTF
GCC
ACC
MCC
Figure 11.4: Notional COP theater.
COP
COP Defined (Cont.)
As discussed in earlier topics, military operations today require all branches of the military to operate and fight in a Joint Environment (Figure 11.4). Therefore, they must be able to integrate their land, air and sea forces into one functional and effective fighting force. The Common Operational Picture (COP) is a concept in which software applications and network communications are used by military participants to achieve that objective.

6. Common Operational Picture
BGDBM - Navy only
2400 bps
OS-OTG format – NECC, TCP/IP (NETPREC)
Limited to 999 shared tracks (track block = )
Dictated Management CT
Participant
COP - Joint Forces
Min. of approx. 64kbps
Binary format-TCP/IP (CST)
Unlimited shared track capability (track block = time stamp)
Distributed management
Figure 11.5: COP and BGDBM comparisons.
CENTCOM
COP / BGDBM Comparisons
In contrast to the COP, Battle Group Database Management (BGDBM) is a Navy concept only. BGDBM is a track management process that enables a SG Common Tactical Picture (CTP) – Manager to manage the platform track portion of the maritime CTP. When you compare the COP to BGDBM, you soon discover several significant differences between the two track management processes (Figure 11.5).
The first major difference is the way GCCS machines exchange data. In a COP environment, GCCS-M uses a software application called COP Synchronization Tools (CST or COP Sync Tools) to exchange data with other machines. The CST application exchanges data in binary format. This binary format is not man readable, so no messages are stored in a machine’s Incoming Message Log (ILOG). Additionally, CST does not support all GCCS-M message types (e.g., OPNOTES). In contrast, BGDBM configured machines exchange data using a man readable message format called Over-The-Horizon Gold (OTG). The OTG message format supports most GCCS-M message types, and its messages are stored in a machine’s ILOG/OLOG for viewing.
The OTG message format also helps highlight another difference between COP and BGDBM - connectivity. To send and receive data, CST uses TCP/IP protocols exclusively; so a machine running CST must be able to connect to the SIPRNET. Whereas in BGDBM, a machine can, in addition to SIPRNET, send and receive OTG messages via other means (e.g., Navy EHF Comms Controller).
CJTF
ACC
GCC
MCC

7. COP NODES TOP COP PARENT CHILD CHILD PARENT CHILD
Figure 11.6: COP Nodes.
Another major difference between COP and BGDBM is how track data is managed. The COP concept uses a decentralized management model (or distributed), while the BGDBM concept uses a centralized management model (dictated). Under the COP concept, nodes are granted, or denied, permissions that allow them to merge, delete and update tracks. Whereas the BGDBM concept uses a centralized track management scheme (i.e. Coordinator (CT) unit) to control all track management functions.
COP Nodes
TOP COP: TOP COP is a title reserved for a Theater Combatant Commander’s (COCOM) COP manager who owns the TOP COP server and is the highest authority in the architecture and topology. The TOP COP server is the machine that has all CST chain management capability.
PARENT NODE: A Parent is a node physically placed over another and may have up to four child nodes. A Parent node has CST management capability over assigned nodes.
CHILD NODE: A Child is a node physically placed under another node (Parent or Child) and has no CST chain management capability.
CHILD

8. Notional BG Architecture
CENTCOM
Notional BG Architecture
CJTF
ACC
GCC
MCC
CSTMdxNET COP CV
FOTC/UID
Figure 11.7: Notional CSG BGDBM/COP architecture.
Notional CSG COP / BGDBM Architecture
Figure 11.7 depicts the traditional FOTC-based BGDBM for the Carrier Strike Group (CSG). Additionally, it shows the CSG flagship participating in a theater COP. In order to function in this dual capacity, the carrier’s GCCS-M is placed in the FOTC/UID Mixed mode.
NETPREC BGDBM CG DD
DDG PT PT PT

9. Notional BG Architecture
CENTCOM
Notional BG Architecture
CJTF
ACC
GCC
MCC
CSTMdxNET COP
CSTMdxNET CV CG
FOTC/UID
Figure 11.8: Multiple CSTMdxNET channels.
Multiple CST channels
Figure 11.8 shows a CSG ship detached from the strike group but participating in a COP with the flagship. In this example, the flagship has two CSTMDXNET channels built and running. The CV is a child node to the MCC, but a parent node to the detached CG.
This method was first employed by USS ABRAHAM LINCOLN, USS SHILOH and USS PAUL HAMILTON in the fall of LINCOLN used the additional CST channel to enable SHILOH and PAUL HAMILTON to CST their link pictures back to the carrier while the ships were detached from CSG. The primary benefit for doing this is that it can provide the flagship a pseudo-link picture of the activity around the detached ship without having to establish a satellite link (or HF) channel.
NETPREC BGDBM CG DD
DDG PT PT PT

10. COP SYNC TOOLS (CST) Comms COP Sync Tools COP Sync Tools
Node List Preconfigure Topology Objects DB Sync Time Sync Owntrack Update Interval Link Assoc Downsample
The pop-up menu
TAKE OWNERSHIP DISTRIBUTE VIA CST TRACK HEADER
Figure 11.9: CST (version x).
COP Sync Tools (CST)
COP Sync Tools is a software application that enables a GCCS-M machine to participate in a COP environment.
Figure 11.10: The GCCS-M communication window.
CST Communications
To enable CST communications, a CSTMDXNET/CSTTCP channel is added. This interface uses the TCP/IP suite of protocols to enable global communications. Figure shows two CST channels built, but the one that is turned on is physically running on jots12.

12. CST DATA TRANSFER TRACKS PRIORITY TRACK DATA (TBM) OVERLAYS
STORED MAPS
STORED PLOT CONTROLS
PIM TRACKS
AIR TASKING ORDERS (ATOs)
AIR CONTROL ORDERS (ACOs)
Figure 11.11: COP – CST’s data exchange capabilities.
Figure 11.12: COP – CST’s track management capabilities.

14. Figure 11.13: The Navy’s COP – CST’s unresolved issues.
NAVY COP – CST ISSUES
BANDWIDTH REQUIREMENT
COMPUTER HARDWARE INTENSIVE
LIMITED TRAINING & DOCTRINAL GUIDANCE
CPU
~ 64 Kbps DEDICATED
SIPRNET
Figure 11.13: The Navy’s COP – CST’s unresolved issues.
COP – CST Issues
In order for the Navy to take full advantage of the COP/CST potential, there are several important issues that still need to be addressed. First, CST’s bandwidth requirement. Since CST sends all of its data using TCP/IP, a COP node must have access to the SIPRNET. If a node needed to pass all of its data via CST it would require a minimum of 64 Kbps dedicated data capacity. Unfortunately, some unit level ships (e.g., FFG) do not have adequate data capacity. Thus, the CST bandwidth requirement makes it highly unlikely that all unit level ships, given their current constraints, would participate in a COP.
The second significant issue is computer resources - specifically, running CST requires a lot of CPU (approximately 80%) and RAM usage.
The last issue is that of Navy-Wide doctrinal guidance and training availability. To help address this issue, a Fleet Integration Syndicate-TADIL/COP (FIS-T/C) was established to continuously coordinate the GCCS-M COP interface and associated policies. The FIS-T/C meets twice a year.

15. Global Command & Control System – Maritime (GCCS-M)
GCCS-M is a single, integrated, scalable Command, Control, Communication, Computer, and Intelligence (C4I) system that receives, displays, correlates, fuses and maintains geo-locational track information on friendly, hostile, and neutral land, sea and air forces and integrates it with available intelligence and environmental information.
GCCS-M provides Tactical Decision Aids that exploit that information.
Figure 11.14: GCCS-M Defined.
GCCS-M
GCCS-M supplies information that aids Navy Commanders in a full range of tactical decisions and in the management of the CTP/COP. There are two GCCS-M variants currently fielded, 3.X and 4.X.
GCCS-M 3.X is the variant that has been around the longest and uses a UNIX based operating system exclusively (i.e. UNIX servers and UNIX workstations).
GCCS-M 4.X is the newer variant which uses UNIX based machines as servers and Windows PCs as workstations.
Another significant difference between the two variants is that 3.X uses Hewlett Packard (HP) servers running the HP-UX operating system while 4.X servers use SUN servers running the SUN SOLARIS operating system.

16. GCCS-M System InterfacesEW
Future
Links
Cryptologic
Navigation
SOA
ADSI/C2P
GALE-Lite
CUB
NECC
NAVSSI
MTC RM
Intel
SLQ-32
CANES
Early Adopter
MIDB
TTWCS
Weapons
System
EPL
ATWCS
Imagery
IPL
GCCS-M
ADOCS
JIVE
JSIPS-N
SQQ-89
PTW+
UAV
TCS-UAV
Figure 11.15: GCCS-M System Interfaces.
MEDAL
Combat
System
P-3
NFCS
Aircraft
GCCS-M (Cont.)
Figure provides a sample of the information systems providing data to/from GCCS-M. GCCS-M currently interfaces with over 54 programs and over 200 segments.
Systems that interface directly with GCCS-M include Tactical Data Links, Electronic Warfare, Cryptologic, Navigation, Weapons Systems, Combat Systems, Weather/Oceanographic, other Command and Control, Simulation & Training, Targeting, Mission Planning, Aircraft, UAV, Imagery, and Intelligence.
NJI
Aegis
GCSS
Mission
Planning
PFPS
GCCS
JMPS
JTT
C4ITTS
METOC
TBMCS C2
Simulation
Targeting
Weather
TRMS
WEBSKED

17. GCCS-M Communications
Network Communications (i.e. TCP/IP)
CSTTCP (4X) / CSTMDXNET (3X)
NETWORK (4X) / NETPREC (3X)
Serial Communications
Navy EHF Comms Controller
TRE-TABULAR / TRE-TAB HIGH
Link Feeds (PLT, ACDS)
NAVSSI
HIT Broadcast
GCCS-M 4.X
Figure 11.16: GCCS-M Communications.
GCCS-M Communications
At its inception, GCCS-M relied heavily upon two UHF SATCOM circuits, OTCIXS and TADIXS A, to disseminate OTH-T track data (i.e. track data embedded in OS-OTG formatted messages) and Mission Data Updates (MDU). However, with the introduction of Information Technology for the 21st Century (IT21) that has changed.
In short, IT21 is an information transfer strategy that uses the TCP/IP suite of protocols to send and receive data across internets. IT21 encapsulates all “data” in IP datagrams and then routes it through the best communications path available (e.g., UHF, SHF or EHF).
The two most commonly used TCP/IP channels in GCCS-M are the NETWORK/NETPREC and CSTTCP/CSTMDXNET channels. Both of these channels use the TCP/IP suite of protocols to exchange OTH track data, Overlays, and ATO/ACO.
In addition to TCP/IP communications, GCCS-M uses numerous serial communication channels. Figure lists some of the more common serial channels.

18. Typical 4.x Force Level Architecture GENSER
OTCIXS
TADIXS A
TRE/CTT/JTT
OTCIXS TTY
TADIXS A TTY
HIT/BOSN
Flt Bcst 1 & 2
Remote Link 11
TRE 2
File/DMDS AD
TES-N RTC
EXCHANGE 2K (2)
NAVMACS/SMS
LAN MUX
Comms1
Webserver
Comms/ADNS
NAVSSI
Comms/ADNS
TBMCS Remote
KSQ-1
Link 11/PLT
Terminal Control
GENSYNC to SCI
OWNSHIP NAV
Sanitized Tracks/RM
ACDS Block 1
Color Deskjet
GENSER LAN (ISNS)
Imagery
Figure 11.17: GCCS-M GENSER 4.x Application Servers
GCCS-M 4.X
GCCS-M 4.X is the next major baseline upgrade for the GCCS-M program and builds on the functionality developed and fielded in the GCCS-M 3.X baseline. GCCS-M 4.X incorporates a transition to the DoD Information Infrastructure – Common Operating Environment (DII COE) 4.0 baseline as well as a migration to Sun Microsystems Solaris and Windows 2000 operating system environments. Figure provides a typical 4.X Force Level Architecture on the GENSER enclave.
4.X Servers
COMMS 1 and COMMS 2: The COMMS servers are Solaris 8 servers that act as the primary communications interface for GCCS-M. COMMS1 is the primary communications server and COMMS 2 is provided as a backup to COMMS 1 and can be manually reconfigured to replace COMMS 1 in the event of a failure.
INTEL/ITS Server: The Intelligence (INTEL) server is a Solaris 8 server that hosts the Sybase relational database. (like jots 19 in 3.X) The INTEL server hosts the General Military Intelligence Database (GMIDB) segment that provides the database structure to store MIDB data. The MIDB 11.0 database contains order of battle, facilities, unit, equipment, and individuals data.
Comms2
B/W Laser
Intel
Imagery PC
PC W/S Dual Eye PC w/s
GBS
CDL-N
Scanner(1)

19. Typical 4.x Force Level Architecture SCI
GENSER LAN MUX in OL-530
Sanitized tracks
EXCHANGE 2K
DMDS
Radiant Mercury AD
Comms1
SCI Common 1
SCI Common 2
TACINTEL A
TACINTEL B
Comms2
(SCI Apps)
Comms/ADNS
LAN MUX
Comms/ADNS
NAVMACS/SMS
GENSYNC
TES-N RTC
SCI LAN
Figure 11.18: GCCS-M SCI Application Servers.
SCI ADNS
Sigs1, Sigs2
4.X Servers (Cont.)
The Defense Intelligence Agency (DIA) is responsible for the MIDB 11.0 database management. The machine that hosts the INTEL server also hosts the Imagery Transformation Server (ITS). The ITS provides cataloging, linking, management, selective archiving, and retrieval of digital imagery and related products. In 3.X, the ITS server is known as jots 14.
Web Server
The web Server is a Solaris 8 server that hosts the Weblogic application server. The application server is used to serve system documentation, in eXtensible Markup Language (XML) format to GCCS-M users. The application server also provides the middle-tier functionality, which isolates GCCS-M users from direct access to Sybase database. The Web Server also typically acts a Print server for GCCS-M. A public key certificate is installed on the web server- it enables connections via SSL protocol.
Color Deskjet
Intel
PC W/S (8-10)
B/W Laser

20. 3.X GENSER Application Servers
UCP & TDBM
Servers
1& 2
IES
JMHS 4
ITS 12 14
GENSER
LAN
Figure 11.19: GCCS-M 3.X Servers.
3.X Servers
JOTS1 & 2 serve as the primary and backup GCCS-M communication servers and enable all of the track database management functions of the common operational picture.
JOTS 4 is the Imagery Exploitation Server (IES): The mission of IES is to provide the imagery analyst with tactical imagery exploitation capabilities. The IES application provides the ability to display, manipulate, enhance, and register imagery. Additionally IES provides advanced tools for linking imagery with MIDB intelligence data and for plotting MIDB intelligence data on top of imagery. (Normally located on JOTS 4 in MSI).
JOTS 12 is the JMHS Server (or Profiling Server): The Profiling Server (PROFSV) segment is loaded once per network and includes the background processes used to profile incoming record messages. It also performs message parsing and storage. This segment provides the server functions for the Profiling Client (PROFCL) and Profiling System Administrator (PROFSA) segments. These functions include: Communications Interface, Header Parsing, Sectional Message Processing, Message Profiling to users and system processes, Message Storage and Cataloging and Message parsing and correlation to MIDB 11.0 for OBREP, IIR, RECCEXREP, TACREP, MISREP, SPIREP. All USMTF formatted messages are processed, routed or stored via this Message Handling Server. 19
ISDS
UCP: Universal Communications Processor
TDBM: Track Data Base Management
IES: Imagery Exploitation Services
JMHS: Joint Message Handling Services
ITS: Imagery Transformation Services
ISDS: Intelligence Support Data Services
JMS: Joint METOC Services 24
JMS
SIPRNET

21. 3. X SCI Application Servers
Radiant Mercury
Sanitization
UCP & TDBM
Servers
UCP & TDBM
Servers
1& 2
GENSYNCH
1& 2
ISDS
JWICS
IES
JMHS
JMHS 19 4
ITS 12 12
SCI
LAN 14 14
Analysis
GENSER
LAN
Figure 11.20: GCCS-M Servers (SCI)
ITS Server
3X Servers (Cont.)
JOTS 14 is the Imagery Transformation Server (ITS). The ITS provides cataloging, linking, management, selective archiving, and retrieval of digital imagery and related products. The ITS Server provides the following functions: executes ITS client application requests, brokers ITS client application requests for data from an Image Product Archive/ Image Product Library (IPA/IPL), provides local imagery data management, provides a local cache for imagery pulled from an IPA/IPL, and creates links between the Imagery and Intelligence databases.
JOTS 19 is the Intelligence Support Data Services (ISDS) Server . ISDS hosts the General Military Intelligence Database (GMIDB) segment that provides the database structure to store MIDB 11.0 data. The MIDB 11.0 database contains order of battle, facilities, unit, equipment, and individuals data. The Defense Intelligence Agency (DIA) is the responsible producer of the MIDB 11.0 database. The ISDS Server also hosts the Central Data Server Web (CDSWEB) segment, which provides a platform and database-independent method for viewing Intelligence Share Data Server (SDS) data. CDSWEB provides a Web-based query capability and displays data from the MIDB 11.0, NID, and IMDB databases. Reports generated by CDSWEB include: Facility Report, Unit Report, Urban Report, Track Report (includes Facility, Unit, Unknown Track, and Ship), Biographic Report, Equipment Report and HELP/on-line documentation. 18 19
ISDS
UCP: Universal Communications Processor
TDBM: Track Data Base Management
IES: Imagery Exploitation Services
JMHS: Joint Message Handling Services
ITS: Imagery Transformation Services
ISDS: Intelligence Support Data Services
JMS: Joint METOC Services 24
METOC
SIPRNET

22. Operational C2 Fleet Gouge
GCCS-M Fleet Liaison Homepage on SIPRnet
GCCS-M Force Advisory Messages (FAMs)
Training Courses
GCCS-M Help Desk
Comm: 1-(800)
DSN:
Figure 11.21: GCCS-M Support.
GCCS-M Fleet Liaison Homepage on SIPRnet
GCCS-M Force Advisory Messages (FAMs)
Posted at above link and sent via regular message traffic - offer workarounds and solutions for GCCS-M operations
Training Courses
Operator – CSCS LS Dam Neck / CSCS LS San Diego
Intelligence – NMITC/FITCPAC
Maintenance – CID LS Norfolk / CID LS San Diego
SYSAD – CID LS Norfolk / CID LS San Diego
Other - OTH-T/C41, C4I System Engineering, and COP Advanced
Operational C2 Principal APM: (858)
Afloat Installation
Assistant Program Mgr: (858)
ILS Manager/
Training Manager: (858)

23. Figure 11.22: TWS Communications.
MDU Delivery
RNI (SIPRNET)
MDU
NECC
STU/STE
EHF Point-to-Point
BGIXS
Track Data
CSTMDXNET
MDXNET
Missile in Flight
TSN
Figure 11.22: TWS Communications.
TTWCS
Tomahawk Weapon System (TWS)
The Tomahawk Weapon System is supported by other C4I systems in multiple ways: through transmission of mission data updates (MDU); Tomahawk Command Information (TCI); and the production of a complete, accurate, timely and precise red, white and blue Common Tactical Picture (CTP). Communication paths for MDU receipt are as follows:
Remote Network Interface (SIPRNET) – TTWCS
MDU attachment (JWICS) – ATWCS
NECC
STU/STE
EHF Point-to-Point
BGIXS (Submarines)
To receive OTH-T track data, ATWCS uses the MDXNET interface in GCCS-M and TTWCS uses the CSTMDXNET interface.
TWS

24. TBMCS Theater Battle Management Core System:
Provides automated command, control, and intelligence system used for planning and executing the air portion of joint operations
Air Planning: Targeting, Airspace, Scheduling
Produces the Air Tasking Order and Air Coordination Order (ATO/ACO)
Monitor/Manage Air Operations
Figure 11.23: TBMCS Defined.
Theater Battle Management Core Systems (TBMCS)
TBMCS is the C4I System for the theater Joint Force Air Component Commander (JFACC). It links various organizational levels of air command, control and execution. TBMCS facilitates air battle planning, intelligence operations and execution functions for all theater air operations. TBMCS provides tasking for all air assets in the Area of Responsibility (AOR) and provides the joint Air Tasking Order (ATO), Airspace Control Order (ACO) and the Air Defense Tactical Operations Data message (TACOPDAT).

25. Portable AIS Equipment
What is AIS?
AIS is a shipboard broadcast transponder system operating in the Very High Frequency (VHF) maritime band that is capable of sending and receiving ship information, including Navigation (Position, Course, Speed …), Identification (Name, Call Sign, Length, Beam …), and Cargo (Draft, Type, Destination …).
Figure 11.24: AIS Defined.
Automated Information System (AIS)
Each AIS system consists of one VHF transmitter, two VHF TDMA receivers, one VHF DSC receiver, and standard marine electronic communications links (IEC 61162/NMEA 0183) to shipboard display and sensor systems. Position and timing information is normally derived from an integral or external global navigation satellite system (e.g. GPS) receiver, including a medium frequency differential GNSS receiver for precise position in coastal and inland waters. 
Other information broadcasted by the AIS, if available, is electronically obtained from shipboard equipment through standard marine data connections. Heading information and course and speed over ground would normally be provided by all AIS-equipped ships.  Other information, such as rate of turn, angle of heel, pitch and roll, and destination and ETA could also be provided.
The AIS transponder normally works in an autonomous and continuous mode, regardless of whether it is operating in the open seas or coastal or inland areas.  Transmissions use 9.6 kb GMSK (Gaussian Minimum Shift Keying) FM modulation over 25 or 12.5 Khz channels using High Level Data Link Control (HDLC) packet protocols. Although only one radio channel is necessary, each station transmits and receives over two radio channels to avoid interference problems, and to allow channels to be shifted without communications loss from other ships. The system provides for automatic contention resolution between itself and other stations, and communications integrity is maintained even in overload situations.
Portable AIS Equipment

26. What are AIS’s Benefits?
Benefits to Navy:
Safety at Sea / Navigation.
Situational Awareness / Common Operational Picture.
Support to Multi-INT Fusion and intelligence gathering (e.g., Open-Source).
Figure 11.25: Benefits of AIS.
AIS (Cont.)
Each station determines its own transmission schedule (slot), based upon data link traffic history and predictions of future actions by other stations.   A position report from one AIS station fits into one of 2250 time slots established every 60 seconds.  AIS stations continuously synchronize themselves to each other, to avoid overlap of slot transmissions.   Slot selection by an AIS station is randomized within a defined interval, and tagged with a random timeout of between 0 and 8 frames.  When a station changes its slot assignment, it pre-announces both the new location and the timeout for that location.  In this way new stations, including those stations which suddenly come within radio range close to other vessels, will always be received by those vessels. 
The required ship reporting capacity according to the International Maritime Organization (IMO) performance standard amounts to a minimum of 2000 time slots per minute, though the system provides 4500 time slots per minute. The Self-Organizing Time Division Multiple Access (SOTDMA) broadcast mode allows the system to be overloaded by 400 to 500% through sharing of slots, and still provide nearly 100% throughput for ships closer than 8 to 10 NM to each other in a ship to ship mode. In the event of system overload, only targets further away will be subject to drop-out, in order to give preference to nearer targets that are a primary concern to ship operators. In practice, the capacity of the system is nearly unlimited, allowing for a great number of ships to be accommodated at the same time.
USS Port Royal

27. Value of AIS At Sea / Ashore / in the Air
Without AIS
170800z Jan
60 contacts
20 min to 72 hours time late
With AIS
Figure 11.26: Value of AIS.
Value of AIS
A specific intention of AIS is to provide tactical decision makers with information to ensure Maritime Domain Awareness. It is important to understand the location of merchant vessels for numerous reasons, some of which include safety of navigation, search and rescue, mission planning, and tracking of high profile targets.
Traditionally the information on “white shipping” trickled into GCCS-M from numerous shore and afloat nodes. Any contact that was not held on an organic sensor (radar, etc) was time-late, and depending on the latency, could be of little value to a tactical decision maker.
To help solve this problem, AIS provides near-real time data that ensures the decision makers have substantial information on which to base decisions.
171600z Jan
1083 contacts
1-5 minutes time late 27

28. AIS CONOPS Overview Notional Architecture within CONOPS (Jan 06)
GENSER
UNCLAS
Sub
Merchant
Rhib
Aircraft
IBS-N
Ship
Coalition
AIS Server
GCCS-M 3.x
Unclassified Subscriber Service
RADIANT
MERCURY
High Assurance Guard
Figure : AIS CONOPS Overview.
GCCS-M 4.x
Notional Architecture
Figure provides the notional architecture for integration of AIS into operational
C2 systems supporting situational awareness within the maritime domain.
CTP feeding Global COP (MDA)
Unclas Server
Non-organic ONI
Shore Site
Notional Architecture within CONOPS
(Jan 06)

29. Tactical Data Links (TDL)
Data Link Terminals
Information Distribution System
JOINT TACTICAL or MULTI-FUNCTIONAL (JTIDS or MIDS)
Data Terminal Set
AN/USQ-125 or Common Shipboard Data Terminal Set (CSDTS)
“MODEM”
Message Processing and Distribution Systems
- Command and Control Processor (C2P)
- Common Data Link Management System (CDLMS)
Common Shipboard Data Terminal Set (CSDTS)
Figure 11.28: TADIL Overview.
Tactical Data Links (TDL)
Tactical Data Links are a composite of automated, tactical data communications systems that provide both one-way and two-way data links for exchange of real time tactical data between units. TDLs include Link 4A, Link 11 A/B, Link 16, and Link 22. The TDLs utilize LOS, Beyond LOS, and satellite communications to provide local as well as theater tactical data exchange.
Link 4A
Link 4A is an automatic, high-speed, computer controlled data link that provides automatic or semiautomatic control of Link 4A equipped aircraft. The Link 4A system provides tactical command, control, target, and navigation data exchange between the controlling station and the controlled aircraft.

30. Multi-TADIL Architecture
EHF/MDR
Intra
and Inter-zone
SG #2
SG #1
Link 16 A
Link-22
Link 16 B
NATO
Link-22
AF/Army
Ship
JTIDS
NATO
Figure 11.29: Multi-TADIL Architectures.
Ship
S-TADIL J
Link-22
Link-11
Link 16
JREAP (
multicast )
unicast
Data
Forwarder
Multi-TADIL Architectures
Figure provides an example of seven links within four Navy Strike Groups (SGs), and illustrates the complexity of the information exchange requirements with connectivity to a shore C2 node.
Multi-TADIL or (Multi-Link Operations) is a method by which CSG/ESG units operate on Link-11A, Link 16, and/or Link 22 depending on the units individual capability. Multi-Link operations allow all units to interoperate across separate links while maintaining a common, cohesive tactical picture.
In short, a CSG/ESG operating in multilink configuration is truly an integrated, single, united data link community, sharing a tactical picture.
Data Forwarding
Multi-Link operations require a CSG/ESG unit to act as the Forwarding JTIDS Unit (FJU) for Link 16 or Gateway Unit for Link 22. Data forwarding is the process of receiving data on one data link (Link 16) and outputting the data onto another data link (Link 11A) in the proper format. Any unit with a C2P can act as the FJU. If a unit is upgraded with the Next Generation C2P it has the capability to become a Gateway Unit between Link 11, Link 16, and Link 22.
Link 16 D
Command
SG #3
Center
Link-11
SG #4
Link 16 C
UHF
S-TADIL J

31. Link 11 Data Updates
In Link 11 a Net Control Station (NCS) polls each Participating Unit (PU) for data. More PUs increase the Net Cycle Time interval between updates.
PU 7
PU 6
PU 2
NCS Poll 
Figure 11.30: Link 11.
TADIL-A (Link 11A)
Link 11A is an automatic, high speed, computer-to-computer, data link that provides for the exchange of tactical data between Link 11 capable units.
Data from individual unit sensors are entered into a computer processing system (AEGIS/ACDS/SSDS); established as track data; correlated with existing tracks; evaluated and identified by operator and/or preset program parameters; and if it meets the criteria for that unit’s reporting responsibility, the track data is transmitted over Link 11. Units participating in the net (PU) then receive and correlate the data in their Tactical Data Systems (TDS), thus compiling the entire force tactical picture in the TDS of each PU.
Satellite Link 11
Satellite Link 11 can operate in either a one-way or a two-way configuration. When operating Link 11 in one-way configuration, all data received on the audio/RF network is simply retransmitted via a satellite. A one-way satellite link may be established using a dedicated 25 KHz satellite channel or over a 2400 bps DAMA channel.
A two-way satellite link may be needed when HF or UHF LOS connectivity is unreliable or participants are out of range. A two-way link requires a unit to operate its DTS in mixed mode thus allowing it to forward audio/RF data to the digital interface, and its digital data to the audio/RF interface.
PU 1
PU 3
PU 5
PU 5 Broadcast
PU 4

32. Link 16 Data Updates Link 16 permits JTIDS Units (JUs) to update more
frequently using:
Time Division Multiple Access (TDMA) a technique that allocates
reporting time slots flexibly according to anticipated use, and
Sub-dividing JUs into Stacked Nets on different frequency hopping
patterns, represented by rings below
JU 10
JU 9
JU 2
Figure : TADIL-J.
JU 8
TADIL-J (Link 16)
Link 16 is an advanced TDL that provides for jam-resistant, crypto secure, digital voice and data communications for command, control, and communications. Additionally it provides an automatic, high-speed, computer-to-computer data link capability.
Link 16 provides multiple nets, relative position navigation, aircraft control functions, surveillance reporting and community identification capabilities. Link 16 is used to exchange/distribute encrypted information from scattered sources at a high rate to all required users of that information. Link 16 uses the J-series message format.
S-TADIL-J (Satellite Link 16)
S-TADIL-J is a Navy design for extending the range of Link 16. It implements most of the J-Series messages although those required for network management, air control, and national uses are not implemented. It uses a token passing, round-robin network access protocol. Data rates over S-TADIL-J are much lower than conventional Link 16 rates.
JU 6
JU 7
JU 3
JU 4
JU 1
JU 5 32

33. Figure 11.32: Link Resilience.
If the Link 11 NCS is disabled or destroyed, time and data are lost while
identifying a new NCS, establishing a time reference, and restarting
the Roll Call.
Link 16 has no NCS. It does require a Network Time Reference
(NTR) which devolves to the unit with the highest Time Quality
(7 - 10) or GPS time if the network is designed to accept GPS.
NCS  ?
New NTR; CG with
Time Quality of 14
 Original NTR
Figure 11.32: Link Resilience.
Link Resilience
Link 11 requires a Net Control Station to ensure proper dissemination of real-time track data. If the NCS is disabled or destroyed time and data are lost while identifying and establishing a new NCS, establishing a time reference, and restarting Roll Call.
Link 16 has no NCS. It only requires a Network Time Reference (NTR) which devolves to a unit with the highest Time Quality (7 -10) or GPS time if the network is designed to accept GPS time inputs.

34. Monthly Inport TADIL Exercise (MITE)
MITE provides basic training of Link 11/16/4A proficiency with Multi TADIL inport and/or underway link exercises.
Upon completion of this event, units take credit for the following exercises:
CCC-42-SF - LINK-11 OPERATIONS
CCC-43-SF - LINK-16 OPERATIONS
CCC-44-SF - MULTI-LINK OPERATIONS
CCC-45-SF - SATELLITE LINK 11 OPS
CCC-46-SF - SATELLITE LINK 16 OPS
POC: Afloat Training Group Pacific (ATGPAC), (619)
Afloat Training Group Atlantic (ATGL), (757) X 270
Maximize
participation
in MITEs
Figure 11.33: MITE.
Monthly Inport TADIL Exercise (MITE)
MITE provides an excellent opportunity for testing TDL performance, ensuring operator and technician proficiency in equipment configuration, link establishment, coordination procedures, and troubleshooting.
Post-Deployment briefs routinely show that active participation in MITE and successfully passing a NCTSI “Longlook” prior to COMPTUEX promotes successful link operations while deployed.

35. Figure 11.34: NCTSI Services.
Testing Services
Navy Center for Tactical Systems Interoperability (NCTSI)
- provides testing services that uniquely analyze a unit’s data link readiness. 
Snapshot
Quicklook  
TADIL Operational Verification Longlook (TOV L/L)
POC: NCTSI Detachment One San Diego (619) NCTSI Detachment Two Norfolk (757)
Deploying Group System InteroperabilityTesting (DGSIT)
- provides subject matter experts, while underway, to evaluate and train strike groups
Figure 11.34: NCTSI Services.
Navy Center for Tactical Systems Interoperability (NCTSI)
NCTSI supports strike group operations through unique data link capabilities allowing commanders the ability to analyze data link interoperability in a multi-TDL environment. Specifically they provide:
Snapshot - 10 minute test (per radio – once the link is established) to determine if Link-16, 11, or 4A hardware is operating properly. 
Quicklook - 2 to 4 hour test consisting of a thorough hardware check (snapshot) and a high-level TDL software validation test.
TADIL Operational Verification Longlook (TOV L/L) - A comprehensive (8 to 12 hour) link readiness analysis comprised of hardware (snapshot) and extensive TDL software verification tests.  NCTSI will verify that the unit under test can correctly process the basic system information needed to exchange data for link operation.
Deploying Group System Interoperability Test (DGSIT)
By direction of USFFC/CPF, the DGSIT program provides a team of subject matter experts that evaluate strike group systems, equipment and procedures during underway, operational use.   DGSIT members assist shipboard technicians in correcting problems and provide a considerable amount of OJT while embarked. DGSIT compiles a database of issues – mostly Link – and works to get those issues resolved at the proper level.

36. THIS PAGE INTENTIONALLY BLANK
Questions??
THIS PAGE INTENTIONALLY BLANK