Military Communications Acronyms

Automated Communications-Electronics Operating Instructions (ACEOI) — the automated successor to the legacy paper Communications-Electronics Operating Instructions (CEOI/JCEOI), providing unit communications planners and operators with frequency assignments, call signs, suffixes, expanders, and signal operating instructions in a digital, distributable format used to load tactical radios and to coordinate communications across a force.

"The digital signal operating instructions that load your radios and set your call signs."

ACEOI is what a signal officer or 25-series NCO actually works in — the digital file that contains the frequency hopsets, call signs, suffix/expander tables, and SOI data that every radio in the formation needs to talk to every other radio. The paper SOI/CEOI of the 1990s has been replaced by automated tools that generate the ACEOI, distribute it, and load it into the SINCGARS/HMS-family radios via fill devices. To a battalion S-6, ACEOI is the artifact they publish before every exercise and every deployment; a bad ACEOI means a unit goes COMMs-out at the worst possible moment. The acronym is signal-officer territory and shows up in every signal annex of every OPORD.

The current DoD protected satellite communications constellation, providing anti-jam, low-probability-of-intercept and low-probability-of-detection communications at extremely high frequency (EHF) for strategic and tactical users, replacing the legacy Milstar system.

"The current DoD protected EHF satellite constellation."

AEHF satellites began launching in 2010 and provide the protected (anti-jam, LPI/LPD) layer of MILSATCOM that strategic nuclear command and high-end tactical users rely on. The constellation operates in geosynchronous orbit and is shared with several US partners (UK, Canada, Netherlands) under cost-sharing arrangements. AEHF supports the same protected mission as Milstar with substantially greater capacity per satellite. Space Systems Command operates the constellation.

Air Force Spectrum Management Office (AFSMO) — the Air Force office responsible for managing the electromagnetic spectrum resources used by Air Force systems, including frequency assignment, spectrum certification of new equipment, host-nation coordination for overseas operations, and representation of Air Force spectrum interests in joint and national-level spectrum forums.

"The Air Force office that manages spectrum allocation and frequency assignment."

AFSMO is the Air Force office that says "yes you can transmit on that frequency in that country at that power" — the spectrum managers who certify new radios, who coordinate frequencies with host nations for overseas operations, and who represent the Air Force in the joint spectrum management process at JFHQ-DODIN and at the national level with NTIA. Spectrum is finite and contested; AFSMO is the back office that keeps Air Force radars, radios, satellite links, and EW systems legally on the air. To a 17S cyberwarfare officer or a spectrum manager at a wing, AFSMO is the parent organization for the certification packages they're working; to most airmen, AFSMO is invisible until a host-nation spectrum dispute kills a training event.

A maritime VHF radio system that automatically broadcasts a vessel's identity, position, course, speed, and other navigational information to nearby ships and shore stations, mandated by IMO SOLAS for commercial vessels above defined size thresholds.

"A maritime VHF system that broadcasts vessel identity and position."

AIS lets ships see each other and lets coastal authorities see the maritime traffic picture in real time. The US Coast Guard operates Nationwide AIS receivers; Navy and CG units exploit AIS for maritime domain awareness; commercial shippers use AIS for collision avoidance and route planning. Adversary vessels regularly turn AIS off (or spoof it), which is itself an indicator — "dark vessels" are a maritime intelligence target. The system is unclassified and broadly available; consumer apps render the same data tourists use to follow cruise ships.

Automated Manifesting System-Tactical (AMS-TAC) — the tactical-level Air Force aerial port automated information system used to build passenger and cargo manifests, generate load plans, and produce the documentation required for air mobility missions at expeditionary aerial ports and during contingency operations.

"The tactical aerial port software used to build manifests and load plans in the field."

AMS-TAC is the laptop-and-printer version of the aerial port — the application aerial port airmen run on a deployable workstation to build manifests, generate 463L load plans, print the paperwork, and feed the data back into the strategic mobility picture. To an Army unit deploying through a bare-base APOE, AMS-TAC is the system the air mobility team is typing your roster and your equipment hand receipts into. When it works, you get on the bird with the right paperwork; when the satellite link goes down or the database doesn't sync, your unit sits on the ramp while somebody re-types a 200-line manifest by hand. The acronym is Air Force inside baseball but every joint exercise touches it.

AN/VRC — the Joint Electronics Type Designation System (JETDS) prefix for vehicle-mounted radio communications equipment, where AN denotes Army-Navy (joint) nomenclature, V denotes vehicular installation, R denotes radio, and C denotes communications; the family includes legacy SINCGARS sets (AN/VRC-90, AN/VRC-92) and modern JTRS-family vehicle radios.

"The naming family for every vehicle-mounted military radio you've ever seen."

AN/VRC is the JETDS prefix that tells you a radio lives in a vehicle — the legacy SINCGARS AN/VRC-90 and AN/VRC-92 dual sets that mounted in every HMMWV and Bradley turret for three decades, the AN/VRC-103 HF dual long-range set, the newer JTRS-family AN/VRC-119 and AN/VRC-118 radios that replaced them. To a 25U or 25C signal soldier, AN/VRC numbers are vocabulary: which set is in which vehicle, which antenna, which mount, which power amplifier. To a tank crewman or a scout, AN/VRC is just "the vehicle radio" — the green box that either works or doesn't when you key the mic. The JETDS scheme (AN/PRC for manpack, AN/VRC for vehicle, AN/GRC for ground-mounted) is one of those military naming conventions that, once learned, you read effortlessly forever.

A Harris/L3Harris-developed wideband software-defined networking waveform used on PRC-117G and related multiband radios, providing higher-throughput IP-based mobile ad-hoc networking at the cost of larger radio form factor and higher power consumption — historically the workhorse data-mesh waveform on 117G-equipped formations.

"The Harris wideband mesh waveform — high throughput, big radio."

ANW2 is the wideband waveform that made the 117G a network node and not just a radio — IP-based, mesh, capable of moving meaningful amounts of data (file transfer, situational awareness updates) over the air. It worked, but it required the 117G form factor (manpack-class power and antenna) and it has been gradually supplemented by smaller-form-factor mesh waveforms (TSM in particular) as the radio family modernized. ANW2 is still in use on 117G-equipped formations and remains a credible high-throughput option when conditions permit.

Air Operations Database (AODB) — the air operations center's authoritative relational database of joint air operations data, including the ATO, ACO, friendly and enemy order of battle, target nominations, and ISR collection plans, used as the data backbone for theater battle management core systems (TBMCS) and follow-on air C2 software.

"The AOC's master database that holds the ATO, ACO, and joint air picture."

AODB is the air operations center's system of record — the relational database that holds the ATO lines, the ACO, the target list, the friendly and enemy order of battle, the ISR collection plan. To an AOC weapons officer, intel analyst, or ATO production specialist, AODB is the back-end every C2 application is reading from and writing to (TBMCS historically, the JADC2 follow-on systems now). When the AODB has integrity, the air picture is coherent; when it doesn't, planners are working off three different spreadsheets at the same kill-chain step. The acronym is AOC inside baseball but it is load-bearing — every line on the ATO came out of the AODB.

All Partners Access Network (APAN) — the U.S. Department of Defense's unclassified information-sharing platform that provides collaboration tools (web, file sharing, forums, wikis) to U.S. and international military, civilian, government, and non-governmental partners, hosted and managed by U.S. Indo-Pacific Command on behalf of the joint force.

"The unclassified DoD platform for sharing info with international and interagency partners."

APAN is the unclass collaboration space DoD uses to talk to people who can't get on SIPR or NIPR — coalition partners during an exercise, NGOs during a humanitarian assistance/disaster response mission, foreign militaries during a multinational planning conference. To a joint exercise planner running RIMPAC, Cobra Gold, or a HADR response, APAN is where the shared document library, the discussion forums, and the file transfers happen; it's the lowest-common-denominator space where everybody can actually log in. The platform is unclass for a reason — it's designed to share, not protect — so the OPSEC discipline of what goes on APAN versus what stays on NIPR is on the user. INDOPACOM owns the program for the joint force.

The mid-1990s upgrade program to the SINCGARS radio family, producing the RT-1523E/F variants with reduced size and weight, embedded GPS, internal data modem, and improved frequency-hopping performance — the most common SINCGARS variant in modern service.

"The lighter, smarter SINCGARS variant — most fielded radios are ASIP."

When a soldier says "ASIP" they usually mean the RT-1523E or F — the variant that replaced the original RT-1523 brick with a noticeably lighter manpack that has an embedded data modem and GPS receiver. ASIP can pass position-location data (the foundation of legacy BFT integration) and supports the broader SINCGARS frequency-hopping infrastructure. ASIP is what most soldiers actually carry when they carry SINCGARS — the original radios are largely retired. Maintenance/training documentation still says "SINCGARS" generically; in practice the radio in the rucksack is an ASIP.

Allied Spectrum Publication (ASP) — a NATO and combined-communications-electronics-board series of publications, alongside the Allied Communications Publication (ACP) series, that standardizes electromagnetic spectrum management procedures, frequency-coordination methods, and host-nation negotiation frameworks across allied operations.

"NATO's allied spectrum publication series — the spectrum-management cousin to the ACP series."

ASP is the allied-publication series that handles spectrum management — host-nation frequency coordination, allied-radio frequency planning, and combined-arms spectrum deconfliction across coalition operations. To a US Army Spectrum Manager (ASM) deployed to Europe, an ASP reference shows up alongside NATO STANAG references and AAPs when working frequency coordination with host-nation regulators; to a joint communications planner in a coalition AOC, the ASP series is the standards baseline that lets allied radios talk without trampling each other. The acronym is specialized — most service members never see it — but for the spectrum managers and signal officers who do, ASPs are part of the daily working reference library alongside ACPs and STANAGs. The Dictionary lists it because joint and combined doctrine cross-reference the series.

A US joint, allied, and partner-force tactical situational-awareness software application running on Android smartphones and tablets (and a Windows-based equivalent WinTAK and an iPhone version iTAK), providing GPS positioning, mapping, friendly-force tracking, mission command, and broad mission-essential information sharing — developed under DoD and Air Force Research Laboratory sponsorship, with extensive joint operational adoption since the late 2010s.

"The ATAK app — phone-based tactical situational awareness, joint adoption."

ATAK (Android Team Awareness Kit) is the smartphone application that has become the de facto tactical situational-awareness tool across joint and partner-force operations — Android-based (with Windows WinTAK and iPhone iTAK variants), it runs on commercial smartphones and tablets to give individual operators and small units GPS positioning, mapping, friendly-force tracking, mission command, intelligence sharing, and many other functions through a plug-in architecture. The application emerged from Air Force Research Laboratory and broader DoD development; adoption has been organic across SOF, conventional forces, and allied/partner organizations. ATAK has been particularly important in Ukraine operations and broader real-world employment. The system has fundamentally changed how tactical situational awareness works at the small-unit level.

Allied Worldwide Navigational Information System (AWNIS) — a NATO maritime system providing the framework, organizations, and procedures for the collection and dissemination of navigational information (notices to mariners, hydrographic data, restricted-area notices, route information) in support of allied maritime operations, ensuring that allied ships and submarines have access to current and accurate navigation information in the operating area.

"The NATO system that pushes navigation, hydrographic, and maritime safety info to allied ships."

AWNIS is the maritime version of the routine plumbing that keeps a naval task group from running aground or sailing into a closed area — a NATO system that collects and pushes notices to mariners, hydrographic updates, route changes, and restricted-area information to allied warships and submarines. To a Navy quartermaster or a ship's navigator on combined operations, AWNIS products show up alongside national NTM (Notice to Mariners) and IMO products as the working pile of paper (and now digital) that goes into the daily nav brief. Submarines in particular live and die by accurate hydrography. To a coalition maritime planner, AWNIS is one of the systems that has to be plumbed before a multinational task group can be combat-ready in shared waters.

A DoD-wide situational-awareness capability providing near-real-time position reporting of friendly forces ("blue forces") via L-band satellite communications and the EPLRS legacy and JBC-P modern terminals — the icons-on-a-map system that lets commanders see where their formations are in real time.

"The friendly-forces tracking system — blue icons on the C2 map."

BFT is the icons-on-the-map capability that became indispensable in Iraq and Afghanistan — every vehicle gets a transponder, and L-band satellite picks up the position reports and pushes them into the common operating picture. JBC-P is the modern terminal (replacing the legacy FBCB2-BFT); the underlying network and concept are the same. BFT is what stops blue-on-blue fratricide and lets a battle captain see where the platoons are without radio check-ins. It is also high-signature: the position reports are visible to anyone with the right collection capability, which has become an operational concern in modern threat environments.

Battlefield Information Collection and Exploitation System (BICES) — a NATO-wide classified information system providing the network, infrastructure, and applications for sharing intelligence and operational information among NATO nations and partner forces at the SECRET level, enabling coalition operations, common operational picture sharing, and combined intelligence collaboration across allied headquarters and deployed units.

"The NATO SECRET-level network for coalition intel and operational information sharing."

BICES is the network US service members in NATO billets, on combined deployments, or in coalition headquarters end up working on every day — the NATO classified system that lets a US officer in a NATO operations center share intelligence with German, Polish, Italian, and Turkish counterparts at the SECRET level without leaving the system. It is not SIPR, it is not JWICS, it is the coalition layer that runs in parallel. To a 35-series intel professional on a NATO assignment or on a multinational deployment, BICES is the credential they get added to and the workstation they sit at; to a US-only-cleared service member who has never worked in a coalition headquarters, BICES is the system that explains why their NATO counterpart can talk freely about a topic the US side has to release through formal channels. Releasability, foreign disclosure, and write-for-release habits are the working art around BICES.

A communications-link characterization indicating that the link operates over distances that exceed direct line-of-sight propagation — typically achieved via satellite communications (UHF SATCOM, MUOS, WGS, AEHF), HF skywave propagation, or relay through intermediate nodes — distinguishing the link from LOS (line-of-sight, direct path) and NLOS (non-line-of-sight, blocked but short-range).

"A communications link that reaches beyond direct visual line."

BLOS is the planning term that distinguishes "we need to talk over the horizon" from "we need to talk to the next ridge." BLOS implies SATCOM, HF skywave, or a relay chain — and each of those carries planning, infrastructure, and signature implications. A platoon talking to its battalion from another valley is doing BLOS; a platoon talking to the next squad over isn't. The terminology shows up in signal estimates, communications plans, and PACE (Primary/Alternate/Contingency/Emergency) planning — you build BLOS into your PACE deliberately because it costs more (terminals, access, frequency management) than LOS.

A communication technique used in DoD written and verbal correspondence that places the conclusion, decision, or required action at the start of the message, followed by supporting context and detail. BLUF is codified for Army correspondence in AR 25-50 (Preparing and Managing Correspondence) and is taught across the joint force as the default email and staff-paper convention.

"State your point first. Leadership can act on it without reading the whole email."

Whoever is reading your email has ninety seconds, max. Bury the ask in paragraph three and it dies in paragraph one — the colonel scrolls to the next message and your request quietly evaporates. BLUF is what separates the staff officer whose tasking gets approved from the one whose tasking gets "see me." Lead with the verb: "Request approval to," "Recommend we," "Decision needed by Friday." Everything else is justification, and justification belongs below the line. The same rule holds for storyboards, CONOPs, and the dreaded read-ahead — if the boss only reads the first three lines, those three lines have to carry the whole thing.

Communication, Authentication, Location, Intentions, Capabilities, and Survivability (CALICS) — a personnel recovery brevity framework used by isolated personnel and recovery forces during the authentication and intentions phase of a recovery event; provides a standardized sequence of information categories the isolated person and the recovery force exchange to confirm identity, locate the survivor, and plan the recovery action.

"The personnel-recovery brevity checklist a downed crew and the recovery force run through together."

CALICS is the procedural framework a downed aviator, a separated SOF team member, or any other isolated personnel runs with the recovery force on the radio — Communication established, Authentication challenge passed, Location confirmed, Intentions stated, Capabilities reported, Survivability assessed. Each letter is a discrete information exchange, in sequence, designed to make a stressed and possibly injured survivor work through the categories rather than dump information and miss things. The framework is taught at SERE schools and integrated into combat search and rescue (CSAR) procedures across the joint force. To a recovery-force helicopter crew or a CRO/PJ team, CALICS is the structure that turns a panicked voice on the survival radio into the eight or nine facts the recovery actually needs to execute. The acronym is a reminder that the worst day of someone's life still has a checklist.

Consolidated Air Mobility Planning System (CAMPS) — an Air Mobility Command information system used by mobility planners and schedulers to plan, schedule, and manage strategic and operational airlift, air refueling, and aeromedical evacuation missions; supports the development of mission itineraries, crew assignments, and tail-number scheduling across the AMC fleet.

"The AMC scheduling system that turns mobility taskings into actual aircraft itineraries."

CAMPS is the AMC planning and scheduling workhorse — the system the mission planners and schedulers at Scott AFB and the AMC numbered air forces use to turn a USTRANSCOM tasking into a specific tail number, crew, route, and itinerary. To a C-17 or KC-46 crew, CAMPS is invisible; you just see the mission package come down with the times, the route, the divert bases, and the load. To the major or chief on the scheduling floor, CAMPS is the day job — building the schedule, rebuilding it when an aircraft breaks, rebuilding it again when a crew goes out of crew rest. The system replaced earlier scheduling tools and has gone through generations of its own; mobility planners who came up in the 2000s remember the predecessors. CAMPS sits inside the broader AMC C2 stack alongside GDSS and 18 AF systems.

Combined Communications-Electronics Board (CCEB) — a five-nation military communications-electronics body (Australia, Canada, New Zealand, United Kingdom, United States — the Five Eyes nations) that develops, approves, and promulgates combined communications-electronics standards, publications, and procedures for use among the member nations' military forces in combined operations.

"The Five Eyes communications standards body — sets common comms rules across US, UK, CAN, AUS, NZ."

CCEB is the five-nation military comms standards body that makes Five Eyes interoperability work — the institution behind the ACP (Allied Communication Publication) series, joint message text formats, common cryptographic procedures, and the rules that let a US signaler hand a UK signaler a TACSAT plan and have it actually work. To a SIGO at a Five Eyes combined headquarters, CCEB publications are the comms bible; the joint network plan, the brevity codes, the authentication procedures, the COMSEC handling rules — all flow from CCEB-approved documents. To a junior signaler at a US-only formation, CCEB is invisible until they get attached to a coalition exercise and discover that "Five Eyes interop" rests on decades of patient standards work. The body sits inside the broader AUSCANNZUKUS communications cooperation arrangement.

The portion of the Cyber Mission Force whose teams are aligned to and operate in support of geographic and functional combatant commanders to provide offensive and integrated cyberspace effects in support of named operations and contingency plans, as established under US Cyber Command and elaborated in joint cyberspace doctrine.

"The CMF teams that hand cyberspace effects directly to a COCOM commander."

CCMF is the slice of the Cyber Mission Force that is COCOM-aligned — the Combat Mission Teams (and their supporting CSTs) that don't sit at Fort Meade defending DoDIN, they ride with INDOPACOM, EUCOM, CENTCOM, AFRICOM, SOUTHCOM, and the functional combatant commands to plan and deliver offensive cyber effects into the theater scheme of maneuver. The other slices of the CMF are the National Mission Force (CNMF, threats to the nation), the Cyber Protection Force (defense of DoDIN), and the Cyber Support Force (analytic, planning, and intel support). CCMF teams are how a four-star theater commander gets cyberspace effects integrated alongside fires, ISR, and information operations — the operational tempo is briefings to J3s and synch with kinetic targeting, not the SOC-watch tempo of the defensive side.

The commander's deliberate, integrated, and synchronized communication with internal and external audiences — comprising public affairs, command information, key leader engagement, and supporting information-related capabilities — to communicate the commander's intent, narrative, and priorities in support of operations and mission objectives.

"How the commander deliberately shapes what subordinates, partners, and audiences hear."

CCS in the joint doctrine sense is commander's communication — not a system, a practice. It's the deliberate effort by the commander and the staff (PAO, IO, the engagement folks, the senior leader engagement cell) to make sure that what the command is saying internally, to partner forces, to host nations, and to public audiences is coherent with intent and isn't getting stepped on by accident. The everyday reality is the command narrative document, the messaging matrix, the talking points for the next KLE, the social-media posture, and the painful work of getting four staff directorates to agree on which words to use in a press release. Done well, it's a force multiplier; done badly, it's the reason the press story about your operation doesn't match the brief you just gave the boss.

A family of DoD-standardized high-bandwidth digital data links used primarily for ISR (intelligence, surveillance, reconnaissance) full-motion video, sensor downlinks, and platform-to-ground/platform-to-platform high-rate data exchange — distinct from the lower-rate tactical data links (Link 16, VMF), with variants including TCDL, SCDL, and MR-TCDL.

"The high-bandwidth data link family — ISR video and sensor downlinks."

CDL is what moves the heavy data — full-motion video off an MQ-9, sensor downlinks from a U-2, high-rate ISR off other platforms. The bandwidth is enough to support actual video and large sensor payloads; Link 16 and VMF can't do that. CDL variants (TCDL for tactical, SCDL for surveillance, MR-TCDL for multi-role) target different platform classes. CDL is line-of-sight (with relay options); the operator-level experience is "the video feed works" or "the video feed doesn't work." The signal/cyber community owns the underlying complexity.

Combined Enterprise Regional Information Exchange System (CENTRIXS) — a family of US-led coalition information-sharing networks operated by the Defense Information Systems Agency and US combatant commands, providing classified data, email, chat, and web services to coalition partners at releasability levels below SIPRNET; instantiated as multiple distinct enclaves (CENTRIXS-FOUR EYES, CENTRIXS-ISAF, CENTRIXS-CMFC/CMFP, others) each scoped to a specific partner set and theater.

"The coalition SIPR — the classified network the US shares with allied partners in theater."

CENTRIXS is what you actually use when you sit down next to a Canadian or Australian or Korean liaison and have to share a graphic, a chat, or an order — not SIPR (which most partners cannot touch) but a parallel network built to a specific releasability set. Each CENTRIXS enclave (FOUR EYES for FVEY, ISAF for Afghanistan, CMFC/CMFP for the Combined Maritime Forces in Bahrain, others) is its own domain with its own accounts and its own portal; if you swap headquarters you swap CENTRIXS variants. To a J6 watch officer or a coalition staff captain, CENTRIXS account provisioning is one of the longest tickets to clear on inprocessing. The network is one of the unglamorous pieces of plumbing that makes US-led coalitions actually work day-to-day.

Combined Electronic Warfare Coordination Cell (CEWCC) — a multinational staff element within a coalition or combined joint task force headquarters that integrates, deconflicts, and coordinates electronic warfare activities across coalition partners and the supported combatant or component command; integrates with the joint Electronic Warfare Coordination Cell (EWCC) and the broader joint electromagnetic spectrum operations cell.

"The coalition version of the EWCC — deconflicts EW across partner nations on a combined staff."

CEWCC is what an EWCC becomes when allies show up — a staff cell at a Combined Joint Task Force or coalition headquarters that has to take the host-nation EW plan, the US plan, and however many partner-nation plans are in the AOR and turn them into a single deconflicted electromagnetic picture. The cell typically runs releasability lower than the all-US EWCC (often on CENTRIXS), maintains the combined Joint Restricted Frequency List with partner inputs, and coordinates jamming approvals across national authorities — each of which has its own legal and political constraints. To an EWO (17B Army electronic warfare officer or USAF 14F equivalent) detailed to a combined headquarters, the CEWCC seat is a coordination job more than a targeting job: the technical knowledge matters, but the political-military judgment about what each partner can authorize matters more.

CG-652 — the United States Coast Guard staff designation (Office of Spectrum Management and Telecommunications Policy) within the Assistant Commandant for Command, Control, Communications, Computers, Cyber, and Intelligence (CG-6) directorate, responsible for radio frequency spectrum management, telecommunications policy, frequency assignment, and spectrum coordination with NTIA, FCC, and partner agencies for Coast Guard operations.

"The Coast Guard office that owns radio frequency spectrum and telecoms policy."

CG-652 is one of those office designations that means everything to a Coast Guard communicator and nothing to anyone outside the Service — the headquarters cell that runs spectrum management and telecommunications policy for the entire Coast Guard, sitting under the CG-6 directorate. Practical effects: when a CG cutter needs a frequency assignment, when a port partner wants to interoperate on a maritime safety net, when the Coast Guard has to negotiate spectrum with the NTIA or the FCC, CG-652 is the office that signs the paper. To a CG OS (Operations Specialist) or IT (Information Systems Technician) at a sector, the office is the source of the frequency authorization documents that make legal radio operations possible. The "CG-652" naming convention (the office of, within the larger CG-6 directorate) is how the headquarters maps its functions; Coast Guard staff designations follow this hyphen pattern throughout.

Collaborative Information Environment (CIE) — the joint information-sharing environment, comprising people, processes, networks, and applications, that enables distributed collaboration among joint, interagency, intergovernmental, and multinational partners during planning and execution of operations; Cultural Intelligence Environment (CIE) — a less-common Dictionary usage referring to the cultural-knowledge frame used in operational planning.

"The shared digital workspace where joint and partner staffs collaborate on planning and execution."

CIE in its primary sense is the doctrinal label for the shared digital workspace a joint or coalition staff uses to actually do its work — SharePoint sites, chat rooms (jabber/mIRC/Slack-equivalents on the appropriate networks), shared planning portals, distributed video teleconferencing, the joint targeting tools — all the connective tissue that lets a CFLCC plans team in one location collaborate with a CFACC plans team in another. The "Cultural Intelligence Environment" reading is a niche secondary usage; in daily staff conversation, CIE means the collaborative environment. To a captain assigned to a CJTF plans cell, the CIE is more important than any single application because if it works the staff can produce a plan in 72 hours; if it doesn't, the staff produces nothing on time. JP 6-0 codifies CIE; the actual implementation varies enormously by headquarters.

Component Joint Data Networks Operations Officer Equivalent (CJE) — a Service component-level officer who fills the joint data networks operations officer role for that component within a combined-joint or joint task force, ensuring tactical data link networks (Link 11, Link 16, Link 22, JREAP, MIDS) are planned, registered, and operated correctly to integrate the component's platforms into the joint network architecture.

"A component-level officer who runs joint data-link networks for their Service in a joint task force."

CJE is one of those Dictionary entries that looks like alphabet soup until you talk to somebody who manages tactical data links — Link 16, Link 22, JREAP, the MIDS terminals on aircraft and ships and ground systems — and then it's clear it's the desk that keeps the components' networks talking to each other on a joint or combined task force. Bad data-link engineering produces ghost tracks, duplicate identifiers, network saturation, and (worst case) blue-on-blue at machine speed; good data-link engineering is invisible. The CJE coordinates with the JICO (Joint Interface Control Officer) at the joint level, runs the Service component's side of the network plan, and certifies the component's units before they go live. The role is technical, niche, and consequential in any kind of contested air, maritime, or integrated air-defense operation.

Coalition Joint Spectrum Management Planning Tool (CJSMPT) — a software application used by joint and combined spectrum managers to plan, deconflict, and coordinate the assignment of radio-frequency spectrum across a multinational joint force, integrating frequency requests from participating units, modeling interference, and producing the Joint Restricted Frequency List (JRFL).

"The software spectrum managers use to deconflict frequencies across a multinational joint force."

CJSMPT is the spectrum-management tool that keeps radios, radars, data links, and EW systems from stepping on each other in a multinational operating area — frequency assignments come in from US Service components and partner nations, the tool models interference geometry and identifies conflicts, and the output feeds the Joint Restricted Frequency List and the daily spectrum management order. The work matters because modern operations are saturated with RF emitters (every UAS, every SATCOM terminal, every counter-UAS jammer, every commercial cell tower in the area) and the deconfliction problem is now harder than during legacy operations. Spectrum managers are a small, technically deep community; the JCMA (Joint Communications Management Activity) at DISA is the parent organization for much of the joint spectrum work. CJSMPT is one of the unglamorous enablers without which the modern joint communications architecture does not function.

A radio operating in a network for tactical command and control communications, typically used for voice communications among ground combat formations at battalion and below — the family of tactical radios (current systems include SINCGARS, HMS Manpack PRC-117G, AN/PRC-148/152 family, AN/PRC-163) operating in the VHF and UHF combat net radio frequency bands.

"Combat net radio — the tactical voice radios at battalion and below."

CNR is the umbrella term for tactical voice radios at the battalion-and-below echelon — the SINCGARS family (the legacy workhorse since the 1980s), the HMS Manpack PRC-117G, the squad and team radios (PRC-148, PRC-152, the newer PRC-163), and the broader set of FM and UHF voice radios that platoon leaders, squad leaders, and team leaders carry. Combat net radio is what soldiers actually use when they say "the radio" — the daily voice procedure of company, platoon, and squad nets that all tactical operations run on. The modernization story (Integrated Tactical Network, leader radios, vehicular intercoms) is changing what CNR looks like, but the basic concept — voice nets at battalion and below — has been continuous since World War II.

Communications network — a general doctrinal term for any integrated set of communications systems, transmission paths, and end terminals that provide command-and-control or information-exchange services within or between joint forces — applied across radio, satellite, wireline, and data networks at all echelons from squad through joint task force.

"A comms network — any integrated set of links and terminals for command and control."

COMNET is the generic doctrinal term for a communications network — could be a tactical FM voice net (the company command net on SINCGARS), a tactical data network (TROJAN, BFT/JCR, JBC-P), a satellite-based reach-back net (PRC-117G to the operations center), or a strategic backbone (DISN, DODIN). The term shows up in doctrine and OPORDs when planners need to refer to a category of communication capability without naming a specific system. Signal officers and S-6 / G-6 staffs build COMNETs as part of the broader communications planning process; the Joint Communications System (JCS) doctrine in JP 6-0 governs how COMNETs at different echelons integrate. Specific net designations (Command Net, Operations and Intelligence Net, Logistics Net, Fires Net) are what subordinate planners actually work with.

Per the DoD Dictionary, common tactical picture — an accurate and complete display of relevant tactical data that integrates tactical information from the multitactical data link network, ground network, intelligence network, and other sources, shared by more than one command and used for tactical decision-making.

"CTP — the shared tactical battle picture used across commands."

CTP is the tactical-level equivalent of the COP — the shared display of friendly, enemy, and neutral positions, sensor tracks, weapon engagements, and other tactical-relevance data that operators across multiple commands see in roughly the same form at roughly the same time. The technology that supports the CTP includes Link 16 tactical data links, MIDS terminals, GCCS-J at the operational level, AFATDS for fires, and a host of service-specific systems plus the joint data integration layer. For the watchstander on a destroyer's combat information center, in an AOC combat ops floor, or in an Army TOC, the CTP is what you're actually looking at; the institutional fight over whose system "owns" the authoritative CTP has been one of the recurring joint command-and-control debates of the past two decades.

The joint family-of-systems concept for processing, exploitation, and dissemination (PED) of intelligence, surveillance, and reconnaissance data — each Service operates its own DCGS variant (Army DCGS-A, Marine Corps DCGS-MC, Air Force DCGS / AN/GSQ-272 SENTINEL, Navy DCGS-N) tied to a common joint architecture for ISR data exchange across Services and with national-level intelligence agencies.

"DCGS — the joint family-of-systems for ISR processing across Services."

DCGS is the umbrella concept rather than a single system — each Service runs its own DCGS variant, all tied to a common joint architecture for moving ISR data (full-motion video from MQ-9s, SIGINT cuts, geospatial products, all-source analysis) between Services and to national-level intelligence. The Air Force DCGS (also known by the AN/GSQ-272 SENTINEL designation) processes most full-motion video; DCGS-A is the Army's analytic backbone; DCGS-MC supports Marine Air-Ground Task Forces; DCGS-N supports naval task forces. The various DCGS variants have had a famously complicated acquisition history — DCGS-A in particular has been politically contested for years — and the integration story across Services has been a long-running joint architecture challenge.

The US Army's variant of the joint Distributed Common Ground System, providing the Army's intelligence analytic backbone for tactical, operational, and strategic intelligence processing, exploitation, dissemination, and analysis — fielded across Army intelligence battalions, brigade S-2 sections, division and corps G-2 sections, and at theater Army Service Component Command intelligence formations.

"DCGS-A — the Army's intelligence analytic backbone, brigade S-2 to theater G-2."

DCGS-A is the analytic system the Army intelligence enterprise runs on — the workstation environment where 35-series intel soldiers process imagery, parse SIGINT cuts, build intelligence summaries, and develop the running intelligence estimate for the commander. The system has been one of the most politically contested major Army acquisitions of the last 15 years: well-publicized criticism from operational users in Iraq and Afghanistan about usability and reliability, the parallel Palantir industry-team competition, and ongoing modernization waves through the DCGS-A Capability Drop releases. For the actual 35F or 35N at a brigade S-2, DCGS-A is the daily workspace — whatever its political history, it's what's on the desk. The system's evolution toward the Intelligence Data Library / common analytic frameworks continues.

The US Marine Corps variant of the joint Distributed Common Ground/Surface System, providing intelligence processing, exploitation, and dissemination capability for Marine Air-Ground Task Forces — fielded across Marine intelligence battalions, MAGTF G-2 / S-2 sections, and Marine expeditionary force intelligence formations.

"DCGS-MC — the Marine Corps variant of DCGS, supports MAGTF intelligence."

DCGS-MC is the Marine Corps slice of the joint DCGS architecture — the analytic environment that Marine intelligence battalions and MAGTF G-2 / S-2 sections use to process the imagery, signals, and all-source intelligence that supports Marine operations. The system shares the broader DCGS data architecture with the other Service variants, which matters because Marine MAGTFs operate as part of joint task forces where intelligence has to flow between Services and national agencies. Compared to DCGS-A, DCGS-MC has had a quieter institutional history — the Marine Corps version benefited from the lessons learned across the broader DCGS modernization without being at the center of the political contention. The capability is what the Marine intelligence community runs on inside MAGTFs and at headquarters.

A Defense Information Systems Agency (DISA) enterprise service providing secure online collaboration capabilities — chat, web conferencing, file sharing, and persistent collaboration spaces — across the Department of Defense at multiple classification levels, including unclassified (DCS) and classified (DCS-S/SIPR) variants used for everyday joint and Service collaboration.

"DCS — DISA's enterprise online collaboration platform across DoD."

DCS is the DISA-operated collaboration platform that does the everyday chat, web conferencing, and file-sharing work across the joint force — the system most service members actually use for cross-organization meetings, persistent rooms, and document collaboration at the various classification levels. The unclassified DCS variant runs on NIPR; the classified DCS-S variant runs on SIPR; the higher classification variants exist on the appropriate networks. The platform has evolved through multiple modernization cycles and has competed with commercial-equivalent solutions (the broader joint shift toward commercial collaboration tools, the Microsoft 365 footprint, and other DoD enterprise services). For most joint staff officers, DCS is one of the windows always open on a SIPR workstation alongside the email client and the relevant operational planning tools.

A Defense Logistics Agency Distribution function providing the mapping, modeling, and visualization of distribution operations across the DLA enterprise — supporting distribution-network planning, in-transit visibility, and analytic support to DLA distribution managers at headquarters, regional, and forward operating levels.

"DDM — DLA Distribution's mapping and visualization function."

DDM is the DLA Distribution function that provides the maps, models, and visualization tools that distribution planners and managers actually use to run the distribution mission — where the stocks are, where they're flowing, what the network looks like at any given time, and how distribution operations connect to the broader joint sustainment picture. The function supports headquarters-level planning, regional distribution operations, and forward DDE elements. For working-level distribution managers, DDM products are part of the everyday picture — the network is too large and too dynamic to manage without strong visualization and analytic support. The capability continues to evolve alongside the broader DLA modernization toward more integrated logistics information systems.

The Department of Defense combat support agency that plans, develops, fields, and supports command, control, communications, and information systems for the President, Secretary of Defense, the Joint Chiefs, combatant commanders, and the services.

"The DoD agency that runs enterprise IT and communications."

DISA runs the DoD's enterprise networks, manages DODIN operations, operates the major data centers, publishes the STIGs, and provides the cloud (milCloud, now DoD Cloud One). When NIPR or SIPR is slow, DISA is one of several possible places to point fingers — though the components, services, and DISA all tend to point at each other first. If you ever need to find DoD IT policy, the DISA Cyber Exchange is the public-facing front door.

The Department of Defense's enterprise telecommunications and information transport infrastructure — a global network of long-haul fiber, satellite communications, and switching infrastructure providing voice, video, and data transport services to DoD components worldwide — operated by the Defense Information Systems Agency (DISA), serving as the underlying backbone for NIPRNet, SIPRNet, JWICS, and other DoD networks.

"DISN — the DISA-operated backbone that carries NIPR, SIPR, and JWICS across DoD globally."

DISN is the DISA-operated backbone that the DoD enterprise networks ride on — the global long-haul fiber, satellite, and switching infrastructure that connects DoD installations across CONUS and overseas, providing the voice, video, and data transport services that NIPRNet (unclassified), SIPRNet (Secret), JWICS (TS/SCI), and the rest of the DoD network architecture depends on. For most service members, DISN is invisible — you log into NIPR or SIPR at your workstation without thinking about the underlying transport — but for DISA personnel, signal soldiers and airmen, and the broader DoD networks community, DISN is the asset whose availability and resilience defines what the rest of the joint force can actually do online. The network has evolved continuously as DoD has shifted toward cloud services, IPv6, and zero-trust architecture; DISN modernization is one of the long-running DISA programs.

The Department of Defense Information Technology Standards Registry — the authoritative DoD register of approved information technology standards, profiles, and reference implementations that DoD systems must conform to in order to be interoperable across the joint force, managed under the DoD Chief Information Officer's standards governance.

"DISR — the DoD-wide registry of approved IT standards every system has to comply with."

DISR is the registry that says, in writing, which IT standards a DoD system is allowed to use — protocols, data formats, message standards, security profiles — and which ones it isn't. For program managers and acquisition shops, DISR compliance is a checkbox on every milestone review, and a system that proposes a non-DISR standard has to justify the deviation in writing. The registry exists because joint interoperability fails when each Service picks its own message format or its own crypto profile, so DISR is the institutional response: a single source of truth, owned by the DoD CIO, that everyone has to point at. The everyday reality is that engineers grumble about being locked into older standards while DISR catches up, and the system owners maintain spreadsheets cross-walking their architectures to DISR entries.

A small, deployable joint or coalition liaison element built around digital communications and battle-management systems, providing a high-bandwidth, fully-networked interface between a parent headquarters and a supported organization (often a coalition partner, multinational headquarters, or non-traditional unit) — designed to extend the parent headquarters' situational awareness and command-and-control into the supported organization rather than relying on voice-only liaison.

"DLD — a digital liaison team that plugs a partner into your headquarters with full network access."

DLD is the modern liaison detachment built around bandwidth rather than around a single liaison officer with a radio — a small team (often a captain or major plus a couple of NCOs and a network sergeant) that deploys with the comms gear to extend the parent headquarters' full common operational picture into a coalition partner, multinational command, or non-traditional unit. The point is that traditional voice liaison can only carry so much, and a peer or near-peer fight requires the supported organization to see what the parent headquarters sees in something close to real time. DLDs have become a recurring fixture in Europe, Indo-Pacific exercises, and combined arms exercises with allies. For the officers and NCOs assigned, the work is part technical (keeping the network up) and part diplomatic (being the face of the parent headquarters inside another organization's battle rhythm).

The Department of Defense's consolidated intelligence information system architecture — the network, computing, and data-management infrastructure supporting the DoD intelligence community, including the Defense Intelligence Agency and the Service intelligence centers — providing the classified information technology environment under which DoD intelligence operates, including elements at the SECRET (SIPRNet), Top Secret/Sensitive Compartmented Information (JWICS), and special-access program levels.

"DODIIS — the consolidated IT architecture for DoD intelligence (DIA, service intel centers)."

DODIIS is the IT architecture that DoD intelligence professionals actually work on — the JWICS terminals at the top-secret/SCI level, the SIPRNet at secret, the analytical tooling, the data lakes, and the connectivity between DIA, NGIC, ONI, NASIC, MCIA, and the combatant command joint intelligence operations centers. The DODIIS Worldwide Conference is the annual gathering where the program offices, system owners, and analysts compare notes on what is working and what is not. For an intelligence analyst, DODIIS is the digital environment work happens in; for the IT and cyber professionals supporting it, the architecture's authority-to-operate, configuration management, and zero-trust transformation are the recurring tasks. The system's capabilities, limits, and friction points are a recurring topic in the intelligence community's honest internal conversations.

The globally interconnected, end-to-end set of information capabilities and associated processes for collecting, processing, storing, disseminating, and managing information on demand to warfighters, policy makers, and support personnel.

"The aggregate of all DoD networks, services, and transport."

DODIN is the umbrella term that replaced "Global Information Grid" (GIG). It covers NIPR, SIPR, JWICS, the transport layer, satellite links, and the data centers that hold all of it — managed in theory by DISA and the components, in practice by a lot of people who do not always agree on who owns what. When something breaks at scale, "DODIN operations" is the team trying to figure out where in the stack the problem actually lives.

A National Geospatial-Intelligence Agency (NGA) controlled-source geospatial reference dataset providing precise, mensurated point coordinates for targeting and other applications requiring weapons-quality geographic precision — distinct from general-purpose digital map data by virtue of its rigorous source control, accuracy specification, and the targeting-quality coordinates it supports.

"DPPDB — NGA's precision-targeting coordinate database, weapons-quality geospatial source."

DPPDB is the controlled-source geospatial reference that NGA produces specifically to support weapons-quality coordinate generation — the dataset a targeteer pulls from to get the mensurated coordinates that go into a JDAM mission or a cruise missile plan. The data is not the everyday digital map a planner uses; it is the rigorously sourced, accuracy-specified reference layer that supports the targeting process under JP 3-60 doctrine. Access is restricted to authorized targeting personnel and the database is one of the institutional foundations that makes GPS-aided weapons accurate. For an intelligence-community geospatial analyst or a joint targeting cell member, working in DPPDB is the day-to-day mechanics of producing the coordinates the strike package depends on.

The Department of Defense global, dedicated, non-secure voice communications network providing unclassified telephone connectivity across DoD installations, deployed forces, and authorized federal partners — operated by the Defense Information Systems Agency (DISA), with worldwide reachability via DSN-prefixed numbering and gateway access from commercial telephone networks.

"DSN — the DoD global voice network, DISA-operated, every base has a DSN prefix."

DSN is the global voice backbone everybody in DoD has used for decades — the unclassified telephone network that connects every DoD installation, deployed headquarters, and authorized federal partner with worldwide reachability. Every duty phone has a DSN number; every contact list has DSN prefixes alongside commercial numbers; every deployed S-3 shop teaches new arrivals which gateway codes get them from the deployed location to a stateside DSN extension. DISA operates the network; the architecture has modernized through multiple waves (analog circuits to VoIP, with the Voice over Secure Internet Protocol equivalent for classified voice). DSN is the unglamorous infrastructure that makes routine joint coordination work. The "DSN ringback" sound is one of the small audio fingerprints of military life.

A standardized military message-format string expressing date and time in a single fixed-length field — formatted as DDHHMMZ MMM YY (two-digit day, four-digit 24-hour time, time-zone letter, three-letter month, two-digit year, e.g. 151430Z MAY 26) — used on every formal military message, operational order, fragmentary order, situation report, and record-traffic transmission to provide an unambiguous time reference across services and time zones.

"DTG — the date-time group on every military message, like 151430Z MAY 26."

DTG is the time stamp on everything formal — every operations order, FRAGO, SITREP, record-traffic message, and Letter of Instruction has one in the header, and it's the thing that lets units across multiple time zones agree on when something happened or when a tasking is due. Z (Zulu) means UTC; the local letter codes (A through Y, skipping J) map to time zone offsets. New soldiers and sailors learn the format the hard way when their first SITREP gets bounced back for using a civilian timestamp instead of a proper DTG. The format is one of the small, persistent ways that military communication enforces precision: the DTG is unambiguous in a way that "Tuesday afternoon" never can be.

A Department of Defense public-affairs platform operated by the Defense Media Activity that aggregates and distributes official imagery, video, news releases, and other public-affairs products from across the DoD enterprise — provides the centralized repository through which journalists, the public, and internal DoD users access official military imagery and reporting on operations, exercises, ceremonies, and other events worldwide.

"DVIDS — the DoD public affairs media library; where official photos and videos live."

DVIDS is the centralized clearinghouse for DoD public-affairs media — the platform where Combat Camera teams upload their footage from operations and exercises, where wing public-affairs shops post unit photos and stories, and where journalists, researchers, and the public download official imagery. The Defense Media Activity at Fort Meade runs the system. For 46-series public affairs Marines, 25V Combat Documentation Soldiers, and the broader PA community, DVIDS is the publication endpoint that makes their products visible — a story that doesn't hit DVIDS effectively didn't happen for external audiences. The platform also serves as the historical archive: years of operational imagery from CENTCOM, INDOPACOM, EUCOM, and elsewhere accumulate there as the public record of joint-force activity.

A formatted, time-sensitive directive transmitted to nuclear-capable forces and other designated recipients, conveying authenticated orders from the National Command Authority through the chain of command.

"A formatted, authenticated directive to nuclear forces."

EAMs are the formatted messages that move through the nuclear command and control system — a specific, authenticated message format used for the time-sensitive directives that the system was designed to deliver. The full content of the system, the operational details, and the specific authentication procedures are classified for obvious reasons; the existence and general purpose are publicly documented. The system has been broadcast for decades and the rotating broadcasts on HF are part of the architecture's public footprint.

The radio frequency range 30-300 GHz, used primarily for high-capacity protected SATCOM (AEHF, Milstar legacy) supporting strategic and theater-level command-and-control with strong anti-jam and low-probability-of-intercept characteristics — accessed via specialized terminals, not by tactical HMS-family handhelds.

"The 30-300 GHz band — protected strategic SATCOM (AEHF) lives here."

EHF is the band that carries the most-protected SATCOM traffic — Milstar (legacy) and AEHF (modern) constellations operate in EHF and provide the strong anti-jam, low-probability-of-intercept, nuclear-survivable command-and-control that strategic and theater leaders rely on. EHF terminals are big and specialized; an infantry platoon does not have an EHF radio. The band is reserved for high-end command-and-control, nuclear C2, and other missions where protection matters more than convenience. Atmospheric absorption (rain fade, oxygen lines) is a real constraint at EHF frequencies.

A radio communications or sensor mode that exploits propagation conditions (atmospheric ducting, troposcatter, specific antenna geometries) to achieve connectivity at ranges beyond the normal line-of-sight horizon — typically used in tactical communications and sensor systems where satellite or HF alternatives are unavailable or contested.

"Radio or sensor mode that reaches beyond the visible horizon via propagation tricks."

ELOS is the propagation regime that gets you communications or sensing past the normal line-of-sight horizon without relying on satellites or HF skywave — exploits atmospheric ducting (a temperature inversion that creates a waveguide low in the atmosphere), troposcatter (forward scatter off the troposphere), or specific antenna-height geometries that extend the geometric horizon. In a contested EMS environment where SATCOM is jammed or denied, ELOS modes become tactically important because they're the only path that keeps tactical-level comms alive between widely separated units. The S-6 / G-6 / J-6 communications planner working a peer-adversary scenario thinks hard about ELOS options; in a permissive environment with full SATCOM access nobody thinks about it. Modern radios increasingly include ELOS-capable waveforms.

The legacy US Army mission command terminal for mounted and dismounted forces from the late 1990s through the mid-2010s, providing friendly-force tracking, digital messaging, and mapping — the system that introduced "icons-on-a-map" digital battle command to the Army before being replaced by JBC-P.

"The legacy Army battle-command terminal — replaced by JBC-P."

FBCB2 is the system that defined Army digital battle command for a generation — every Iraq/Afghanistan veteran knows the green screen and the "FBCB2-BFT" capability that paired it with friendly-force tracking. The system was revolutionary when fielded and obsolete by the time it was retired. JBC-P replaced it across the force in the mid-2010s. FBCB2 still appears in older training materials and historical references; if a Veteran mentions "Blue Force Tracker on the FBCB2," they're describing the legacy era. The lessons learned from FBCB2 (interface complexity, training burden, the gap between "capability exists" and "capability used effectively") shape current mission-command system design.

The capability and process of digitally tracking the location of friendly forces in near-real-time across the operational environment — provided through GPS-enabled transponders, command and control systems, and the joint blue force situational awareness architecture that fuses position data into the common operational picture used by commanders to maintain situational awareness and prevent fratricide.

"FFT — the digital architecture that puts every friendly platform on the common operational picture."

FFT is the architecture that finally answered the World War II and Desert Storm question of "where are my own units right now" without waiting for a radio report or a map overlay. The Army's Blue Force Tracker (later Joint Capabilities Release / JCR) hangs a GPS transponder and a satellite radio on every vehicle, every command post, and increasingly every dismounted leader; the position data lands in the mission command system and on the commander's tablet as a live blue icon. The payoff is fratricide prevention, faster decision cycles, and shared situational awareness across the joint force; the cost is the electromagnetic signature, the bandwidth tail, and the cultural shift to commanders staring at a screen instead of a paper map. Modern combat against peer adversaries who can geolocate emitters has reopened the question of when FFT helps and when it hurts.

A message format used in tactical and operational communications in which the content is not constrained to a pre-defined format — used for narrative reporting, situation updates, and other communications that do not fit into formatted message traffic such as the US Message Text Format (USMTF) or the various joint reporting structures.

"FTM — the unstructured message format used when formatted traffic (USMTF, joint reporting) doesn't fit."

FTM is the escape valve in formatted comms. Most operational traffic flows in structured formats — USMTF, joint reports, AFRTS reporting, message text formats with mandatory fields and parsing rules — because automated systems can read them, fuse them with other reporting, and route them appropriately. When the situation doesn't fit any of those structures (a unique observation, a complex incident, a narrative the commander wants verbatim to the higher headquarters), the operator drops to a free text message. The trade-off is the loss of automated parsing: a free text message gets read by a human, distributed by a human, and frequently re-keyed into a structured system later. Most operators learn to write FTMs that mimic the structured fields the destination is going to need, just to save the receiving watch officer the work of pulling it apart by hand.

A US Department of Defense one-way, high-data-rate satellite broadcast service providing wideband imagery, intelligence, weather, video, and other data products to deployed forces — the receive-only milsatcom capability that pushes large data products from the production rear to the consuming forward node without consuming the bandwidth of bidirectional satellite links — fielded across the joint force with terrestrial receive suites at deployable and fixed sites.

"GBS — the one-way DOD satellite broadcast that pushes big data to deployed forces."

GBS is the satellite TV of the joint force — receive-only, one-way, high-bandwidth, designed to push the big data products (imagery, full-motion video, weather, intelligence dumps, software updates) to forward consumers without burning the precious bidirectional milsatcom bandwidth that operational comms depend on. A deployed intel cell or a tactical operations center sets up the GBS receive antenna, points it at the right satellite, and starts pulling the broadcast streams it is authorized to receive. The capability solves the bandwidth-asymmetry problem of deployed operations: a forward user mostly wants to receive a lot of data, not send a lot, and a one-way broadcast architecture is enormously more efficient than treating every data pull as a bidirectional request. GBS has been around since the late 1990s and is part of the broader milsatcom architecture alongside DSCS, WGS, and the protected SATCOM family.

The US Department of Defense joint command and control system of record (initial fielding mid-1990s, with continuous modernization through the GCCS family of Service and joint variants) — providing the common operational picture, force tracking, mission planning, and joint command and control applications across the combatant commands and the Services — the C2 backbone that replaced the legacy World Wide Military Command and Control System (WWMCCS) and has anchored joint C2 since.

"GCCS — the joint command and control system of record since the mid-1990s."

GCCS is the joint C2 system every operations watch floor has been built around since the mid-1990s — the platform that replaced the older WWMCCS (World Wide Military Command and Control System) and became the common operational picture, force-tracking, and joint command-and-control backbone for combatant command and Service operations centers. The system spawned a family of variants tailored to specific user communities (GCCS-J at the joint level, GCCS-A for the Army, GCCS-I3 for the integrated imagery and intelligence community, GCCS-M for the Navy maritime version) all sharing the same underlying C2 architecture. The system has been modernized continuously and is in transition toward newer C2 architectures (JBC2 family), but for an operations officer running a watch floor in the 2020s GCCS-derived applications are still part of the daily workspace.

The US Army variant of the Global Command and Control System family — the Army-tailored implementation of GCCS providing the common operational picture, force tracking, and command and control applications scoped to Army operations from theater Army down through corps and division — fielded across Army operations centers as the Service-level C2 backbone that links to the joint GCCS-J architecture.

"GCCS-A — the Army flavor of GCCS, tailored to Army echelons."

GCCS-A is the Army-tailored variant of the joint GCCS family — same architectural backbone, same common-operational-picture concept, but configured for Army operations and Army echelons from theater Army through corps and division. The system shows up in division and corps operations centers as the watch-floor C2 platform that links to the joint GCCS-J, that hosts Army-specific applications, and that handles the unit identification, force tracking, and mission-planning needs that an Army operations officer brings to the floor. GCCS-A is being progressively modernized within the broader command-post computing-environment transition (CPCE and successors), but the GCCS-derived applications and the family lineage continue to anchor Army C2 in the watch-floor environment.

The integrated imagery and intelligence variant of the Global Command and Control System family — providing imagery exploitation, geospatial intelligence, and integrated all-source intelligence applications within the broader GCCS architecture — the intelligence and imagery-fused C2 capability that links the GEOINT and all-source intelligence community to operations-center common operational pictures.

"GCCS-I3 — the imagery and intelligence-integrated flavor of GCCS."

GCCS-I3 is the imagery and intelligence-fused variant of the GCCS family — the version that links GEOINT imagery, all-source intelligence, and the operations-center common operational picture into a single workspace. Imagery analysts and operations officers working a watch floor where intelligence and operations have to be tightly coupled (combatant command headquarters, theater joint intelligence operations centers, joint targeting elements) use GCCS-I3 to pull imagery products and integrated intelligence overlays into the operational picture rather than working two separate systems. The variant is one piece of a broader GEOINT enterprise architecture that includes NGA's production systems and the analytical workspaces of NSA and the broader IC; GCCS-I3 is the operations-side bridge.

The joint variant of the Global Command and Control System family — the joint-level implementation of GCCS providing the common operational picture, joint force tracking, and joint command-and-control applications for combatant command and joint task force operations centers — the C2 platform of record for joint operations watch floors at the combatant command and joint task force level.

"GCCS-J — the joint flavor of GCCS, the COCOM C2 platform of record."

GCCS-J is the joint variant of the GCCS family — the operations-center C2 platform that combatant command and joint task force watch floors have been running since the late 1990s. The system gives the combatant commander the common operational picture across the Services in the theater, joint force tracking, mission-planning applications, and the broader joint C2 toolkit. Every COCOM operations center, every joint task force watch floor, every JOC running joint operations has had GCCS-J or its successors as the workspace. The system is in slow transition toward newer joint C2 architectures (JBC2 family, the Joint Battle Command Platform family) but the GCCS-J application set and the workflows built around it continue to anchor joint C2 in the 2020s.

The US Department of Defense joint combat support system family — the logistics, personnel, and combat-support information-system backbone that complements the GCCS command-and-control family — fielded as Service variants (GCSS-Army for the Army, GCSS-Marine Corps, GCSS-Air Force) and as the joint GCSS-J integrating the Service systems for joint combat support — the combat-support information backbone that supports the joint force on logistics, supply, and personnel.

"GCSS — the combat support information backbone, Service variants plus joint GCSS-J."

GCSS is the combat-support system family — the logistics, supply, personnel, and combat-support information backbone that runs alongside the GCCS command-and-control family. Each Service has built its own GCSS variant tailored to its logistics and personnel structures: GCSS-Army is the Army's enterprise logistics and supply system (the platform every supply NCO and unit logistics officer touches daily), GCSS-Marine Corps does the same for the Marine Corps, the Air Force has its variant, and GCSS-J integrates the Service systems into a joint combat-support picture. The systems handle property accountability, supply requisitions, maintenance management, transportation movement, and the broader combat-support information that the joint force depends on. For a unit logistics shop the GCSS-Service variant is the daily workspace; the joint GCSS-J is the integration layer above it.

The joint variant of the Global Combat Support System family — providing the joint-level integration of Service combat-support information systems for joint logistics, supply, personnel, and combat-support common operational picture — the joint combat-support information backbone supporting combatant command logistics and joint task force support operations.

"GCSS-J — the joint flavor of GCSS, integrates the Service combat support systems."

GCSS-J is the joint variant of the GCSS family — the integration layer above the Service-specific GCSS variants (GCSS-Army, GCSS-Marine Corps, GCSS-Air Force) that gives a combatant command or joint task force the joint combat-support common operational picture. A joint force logistics officer working a J4 staff or a joint logistics operations center looks at GCSS-J to see the consolidated logistics picture across the Services — supply, maintenance, transportation, personnel — without having to log into each Service's separate system. The system has been progressively modernized as part of the broader joint information systems portfolio; for the joint logistics community it has been a daily workspace for over two decades.

The US Air Mobility Command information system providing real-time and near-real-time air-mobility mission planning, monitoring, and command and control decision support — the air-mobility C2 platform that integrates mission planning, aircraft and crew status, weather, and operational tasking to give Tanker Airlift Control Center (TACC) controllers and supporting nodes the air-mobility common operational picture.

"GDSS — the AMC decision support and C2 system for air mobility missions."

GDSS is the air mobility command-and-control platform that the Tanker Airlift Control Center (TACC) and supporting nodes work in — the system that gives an AMC controller the air-mobility common operational picture: every mission planned, every aircraft tail, every crew status, every weather constraint, every load status, every cargo movement in execution. A TACC controller managing the global air-mobility flow watches GDSS to see where the jets are, what they're hauling, where they're going, and where the next tasking is going to land. The system pairs with GATES (the cargo and passenger transaction backbone) — GDSS owns the mission side, GATES owns the cargo and passenger side. Together they are the air-mobility information backbone for AMC and the broader joint air-mobility enterprise.

A joint message-traffic format used in formatted message systems and Joint Army Navy Air Publication (JANAP) and Allied Communications Publication (ACP) message conventions for free-text content embedded within an otherwise-formatted message — the "general text" set of fields where narrative text content (situation report narrative, operational summary, free-form context) lives within a record-message format that is otherwise highly structured.

"GENTEXT — the free-text narrative fields within a formatted military message."

GENTEXT is the part of a formatted joint message where narrative free text actually lives — the otherwise highly structured record-message formats (USMTF, JANAP, ACP) need somewhere for the narrative content (the situation report paragraphs, the operational summary, the context an operations officer wants to communicate beyond the structured fields), and GENTEXT is that bucket. A communications NCO building a SITREP or a situation update fills the structured fields with the codified content and then writes the narrative into the GENTEXT sections. The format conventions are old (the JANAP and ACP series predate the internet era) and the workflow has slowly shifted toward more modern formats and email-style messaging, but GENTEXT fields still appear in current message formats and continue to be the home for narrative content within otherwise-structured traffic.

A US National Geospatial-Intelligence Agency enterprise information system providing the tasking, processing, and production backbone for geospatial intelligence across the GEOINT enterprise — the system that handles collection tasking against the NGA collection pool, ingests and processes raw geospatial data, and produces the analytical and target-grade GEOINT products that consumers across the joint force depend on.

"GETS — the NGA enterprise GEOINT tasking, processing, and production system."

GETS is the NGA enterprise system that runs the tasking-processing-production backbone of the GEOINT enterprise — when a combatant command, a Service intelligence center, or a joint task force levies a GEOINT collection or production requirement, GETS is the system that routes the tasking, manages the processing flow against NGA collection capacity, and produces the analytical and target-grade products that come back to the consumer. The system is the enterprise version of what individual GEOINT analysts experience at their workstations; for an NGA analyst the system shapes the production workflow, and for a consumer the system shapes what GEOINT products are actually available against the time deadlines the consumer needs. GETS pairs with the GETM product line and the broader NGA enterprise architecture to support the GEOINT enterprise the joint force depends on.

Standardized visual signals (ground-to-air signals) used by ground personnel to communicate with aircraft when radio communication is unavailable, denied, or impractical — including marker panels (VS-17), pyrotechnic signals, mirrors, smoke, and configured ground-marking patterns — used in search and rescue, downed-aircrew recovery, and emergency air-ground coordination.

"Visual signals from the ground to aircraft when radio is unavailable."

GTAS is the fallback set of techniques for talking to an aircraft when the radios are down, denied, or the situation requires silent signaling — the VS-17 marker panel (orange one side, pink the other), pyrotechnic signals (smoke grenades, signal flares, pen-gun flares), signaling mirrors, and configured ground patterns that aircrew know how to read. The skills are core to SERE training, downed-aircrew recovery doctrine, and combat search and rescue (CSAR), and they're emphasized again whenever joint exercises rehearse contested-EMS scenarios where radios may be jammed or compromised. For most service members the GTAS knowledge sits as the chapter of the field manual you've read but never had to use; for SERE-coded aircrew and CSAR operators it's muscle memory.

The radio frequency range 3-30 MHz, propagating beyond line of sight via ionospheric reflection ("skywave") and supporting tactical communications over hundreds to thousands of kilometers without satellite infrastructure — used on PRC-160 and related modern HF manpacks as an alternative to SATCOM.

"The 3-30 MHz band — bounces off the ionosphere, talks long distance without satellites."

HF is the band the joint force is rediscovering — it bounces off the ionosphere ("skywave") and lets a manpack radio talk hundreds or thousands of kilometers without a satellite, which matters increasingly as SATCOM denial becomes a credible threat. HF discipline is hard: propagation depends on time of day, season, solar activity, and antenna selection; effective HF requires planning and skilled operators. The PRC-160 (and the legacy PRC-150) made HF practical for tactical operators with automatic link establishment and wideband data modes. HF is also the band most amateur ("ham") operators work in, which provides a deep skill pool the force is starting to tap again.

A category of tactical radios (hand-held radio) characterized by single-operator carriage, integrated antenna, integrated power source, and the form factor of a handheld unit — distinct from manpack radios (carried in a rucksack), vehicle-mounted radios, and base-station radios — current joint inventory includes AN/PRC-148 MBITR, AN/PRC-152, AN/PRC-163, and successor programs.

"A single-operator tactical handheld radio — PRC-148, PRC-152, PRC-163 class."

HHR is the doctrinal label for the radio class that everybody actually calls "the brick" or "the 152" — a single-operator tactical handheld with an integrated antenna and battery, carried on the chest rig or on a sling. AN/PRC-148 MBITR was the workhorse for years; AN/PRC-152 expanded the capability set; AN/PRC-163 is the current two-channel JTRS-family radio that lets a squad leader monitor company-net and platoon-net simultaneously. HHRs are distinct from manpack radios (AN/PRC-117G / 162 class, carried in a ruck because the antenna and battery are larger), vehicle radios (VRC family), and base station radios. For a squad leader, the HHR is on your chest while the manpack is in the platoon HQ rucksack — the trade-off is range and waveform versatility vs. weight and signature.

The US Army-led joint acquisition program to replace legacy single-channel tactical radios with a family of software-defined multiband radios across handheld, manpack, and small-form-fit (vehicle/aerial) configurations — including the PRC-152, PRC-148, PRC-117G, PRC-158, PRC-163, and PRC-160 variants — running multiple waveforms (SINCGARS, SATCOM, SRW, ANW2, TSM, HF) on common hardware.

"The program that replaced single-mission radios with software-defined multi-band radios."

HMS is the acquisition framework behind every modern tactical radio a soldier carries — the recognition (post-Iraq/Afghanistan lessons-learned) that the legacy "one radio per waveform" approach didn't work when an infantry platoon needed VHF combat-net, UHF SATCOM, and a mesh data network simultaneously. HMS radios are software-defined: the same physical radio can run SINCGARS one moment and a mesh waveform the next, with the waveform loaded as software. The program's acquisition history is messy (contract protests, schedule slips, vendor disputes) but the resulting radios — the L3Harris and Thales families — are what current formations actually deploy with.

A Department of Homeland Security web-based information sharing platform (Homeland Security Information Network) that connects federal, state, local, tribal, territorial, and private-sector partners for sharing sensitive-but-unclassified information related to terrorism prevention, critical infrastructure protection, and incident response — serves as a principal interagency information backbone for homeland security operations.

"The DHS sensitive-but-unclassified information sharing platform for homeland partners."

HSIN is how DHS shares information with everyone outside the federal classified networks — state homeland security advisors, fusion centers, local law enforcement, critical infrastructure private-sector partners, tribal governments, and other non-federal stakeholders who do not have routine access to SIPRNet but need timely homeland security information. The platform hosts community-of-interest portals for specific sectors (transportation, energy, water, health), pushes alerts and advisories, and supports operational coordination during incidents. For DoD personnel supporting defense support to civil authorities or working through NORTHCOM's interface with DHS, HSIN is one of the practical information sharing tools that bridges the classified/unclassified seam.

A dual-meaning DoD Dictionary entry: (1) Integrated Booking System, the USTRANSCOM strategic sealift booking system that schedules cargo movement aboard military and commercial sealift assets; and (2) Integrated Broadcast Service, the multi-source intelligence broadcast that delivers near-real-time tactical and operational intelligence to deployed users via various receiver terminals.

"Either the strategic sealift booking system or the multi-INT intelligence broadcast."

Two unrelated things sharing one acronym. As Integrated Booking System, IBS is the USTRANSCOM workflow that books equipment onto sealift hulls — when a brigade rotates to Europe by sea, the gear gets routed through IBS to a specific ship at a specific port on a specific date, and an SDDC port operator monitors the movement. As Integrated Broadcast Service, IBS is the wideband multi-INT broadcast that pushes near-real-time intelligence (SIGINT cues, missile launch warnings, naval movements) down to tactical receivers like the AN/USQ-167 or various platform-integrated terminals — the kind of feed that warns a destroyer it has a hostile track inbound minutes before a national-level reachback could. Which meaning is in play is always clear from context.

A dual-meaning DoD Dictionary entry: (1) integrated contingency plan, the consolidated planning document used in oil and hazardous material spill response that integrates federal, state, and local response requirements; and (2) intertheater communications pipeline, the strategic communications routing architecture that links combatant command theaters to one another and to the strategic-level command and control infrastructure.

"Either the spill-response integrated plan or the inter-theater comms routing architecture."

Two unrelated things sharing one acronym. As Integrated Contingency Plan, ICP is the consolidated spill-response document that satisfies the various federal (EPA, USCG, OSHA, DOT) and state requirements in a single coordinated package — relevant to DoD installations, fuel depots, and any facility with significant hazardous material storage. As Intertheater Communications Pipeline, ICP is the strategic communications routing architecture that links the various theater communications networks together and to the strategic-level enterprise — managed by DISA and the Joint Staff, and the reason a CENTCOM J3 can talk to an INDOPACOM J3 in a crisis without going around the world by sneakernet. Which meaning is in play is always context-driven.

A dual-meaning DoD Dictionary entry: (1) initialization data load, the set of mission-specific data parameters loaded into a weapon, sensor, or other system at mission startup to configure it for the operational scenario; and (2) integrated distribution lane, a USTRANSCOM-supported sustainment routing concept that combines multiple sustainment flows into common transportation lanes for efficiency.

"Either the mission data load into a weapon/sensor or the combined sustainment routing lane."

Two unrelated things sharing one acronym. As initialization data load, IDL is the configuration upload — target coordinates, frequency tables, friendly-force locations, geofencing, mission parameters — that a weapon, sensor, or comms system takes in before mission start; without it the system is unusable or default-configured. As integrated distribution lane, IDL is the logistics concept of combining multiple sustainment flows (Class I food, Class III fuel, Class IX repair parts, mail, ammunition) into common transportation lanes that USTRANSCOM and theater distribution operators run together for efficiency rather than running parallel single-class supply chains. Which meaning is in play is always context-driven.

A formal documentation construct (information exchange requirement) that defines what information must flow between which organizations, in what format, at what classification, and on what timeline to support a specific operation, plan, or capability — feeds command-and-control system design, interface standards, and the broader C4 architecture documentation under the DoD Architecture Framework (DoDAF).

"The formal documentation of who needs what information from whom, when, and in what format."

IER is the staff-level paperwork that turns "we need to share information with the partner force" into something engineers and architects can actually build to: a defined sender, a defined receiver, a defined data product, a classification level, a latency requirement. The construct lives in the DoD Architecture Framework world (the OV-3 operational view, the SV-6 systems view) and shows up in capability development documents, joint operating environment analyses, and coalition interoperability planning. For an operator IER is invisible until it's missing — the reason your CPOF doesn't talk to the partner-nation system, the reason the targeting cycle has a manual reach-back step, the reason the air picture and the surface picture live in different displays. For a J6/G6 staff officer, IERs are the daily work of making C2 systems actually exchange the right information.

A DoD logistics and transportation information system construct (Integrated Data Environment / Global Transportation Network Convergence) that merged the legacy Integrated Data Environment (IDE) and the Global Transportation Network (GTN) into a unified in-transit visibility and logistics information capability under USTRANSCOM, providing combined logistics and transportation data services for the joint force.

"The merged IDE/GTN logistics and in-transit visibility data environment under USTRANSCOM."

IGC is the back-end logistics-and-transportation information environment that USTRANSCOM built when it consolidated the legacy Integrated Data Environment and the Global Transportation Network into a single capability — provides the in-transit visibility, the logistics data services, and the integration layer that downstream systems (the unit movement officer's tools, the J4's common operating picture, the deploying force's tracking dashboards) consume. For a deploying unit, IGC is invisible but ubiquitous: the reason you can pull up where your container is in the strategic-mobility pipeline, the reason the J4 has a live picture of the deployment, the reason the receiving installation knows what's coming and when. For a logistics information systems professional, IGC is one of the principal consolidation efforts of the post-2010 USTRANSCOM IT modernization.

A standardized HUMINT (human intelligence) raw-reporting product (intelligence information report) used across the Defense Intelligence Enterprise and broader Intelligence Community to transmit raw, source-attributed information from collectors to analysts and consumers — the IIR is single-source, unevaluated, and carries source-reliability and information-credibility ratings — the principal raw HUMINT product that feeds finished intelligence analysis.

"The standardized raw HUMINT report — source-attributed, single-source, unevaluated."

IIR is what a HUMINT collector — a case officer at a station, a HCT team in theater, a strategic debriefer working a defector — produces when they have raw information that needs to get into the analytical and consumer ecosystem. The report is single-source by design (one IIR per source per topic per reporting event), carries the source-reliability rating (A through F) and information-credibility rating (1 through 6), and goes into the central HUMINT reporting databases (DOMEX, HOTR, and the broader IC architecture). Analysts and consumers read IIRs to see the raw picture; finished intelligence products (assessments, estimates) are built by fusing many IIRs with other-INT reporting. For a collector, writing a good IIR is a craft skill — clear, concise, source-protective, properly caveated.

A standardized in-flight reporting message (inflight report) used by aircrews to transmit time-sensitive observations, target information, weather data, or tactical assessments from the airframe back to controlling agencies during a mission — feeds the broader joint operating picture and supports follow-on tasking before the aircraft returns to base.

"The standardized aircrew message for sending observations from the cockpit while still airborne."

INFLTREP is the format aircrew use when they see something — a target of opportunity, an unexpected enemy disposition, a weather phenomenon affecting other missions, a battle-damage assessment of a strike that just went in — that needs to get to the controlling agency now rather than at the debrief two hours later. The report goes over voice or data link to the appropriate command-and-control node (AWACS, JSTARS legacy, the CAOC, the carrier air wing CIC, depending on mission and service), where it feeds the operational picture and may trigger follow-on tasking before the originator even returns to base. For a fighter or recce crew, INFLTREP is part of the standard mission rhythm; for a transport or tanker crew, less frequent but still in the qualification syllabus. The construct predates modern data links by decades and remains relevant because voice-radio brevity reporting is faster than any modern messaging architecture when seconds matter.

A J2/intelligence-staff function (information operations intelligence integration) that provides dedicated intelligence support to information operations planning and execution — analyzes the information environment, characterizes target audiences, identifies adversary information capabilities, and assesses the effects of friendly information operations — the intelligence-side counterpart to the operations-side IO planning function.

"The J2 cell that provides intelligence support to information operations planning."

IOII is the J2 cell that does for information operations what targeting intelligence does for fires: characterizes the information environment, profiles the target audiences (their media consumption, their influence networks, their cognitive vulnerabilities), maps the adversary's information capabilities and likely counter-actions, and assesses whether friendly information operations are actually moving the indicators they were supposed to move. The function exists because the information environment is genuinely hard to assess — measures of performance (we put out the message) are easy, measures of effectiveness (did the audience change its behavior) are very hard. For an IO planner, the IOII cell is the intelligence support that turns a notional theme-and-message into a defensible assessment of audience, vulnerability, and likely effect. For most of the force IOII is invisible — but it is the analytical spine behind credible IO planning.

Two meanings in the DoD Dictionary (November 2021): (1) information-related capability — a tool, technique, or activity employed within a dimension of the information environment that can be used to create effects (the term used for the broad set of disciplines synchronized in information operations); (2) Internet relay chat — a legacy text-based real-time messaging protocol that has appeared in DoD networking and communications vocabulary.

"IRC — information-related capability (IO discipline) or Internet relay chat (chat protocol)."

IRC carries two very different meanings. The information-related capability sense is the joint-doctrine vocabulary for the broad set of disciplines synchronized in information operations — MISO, MILDEC, OPSEC, electromagnetic warfare, cyberspace operations, public affairs, and others. The IOWG (Information Operations Working Group) integrates IRCs at the joint force level. The Internet relay chat sense is the legacy text-chat protocol that has shown up in DoD chat-and-collaboration vocabulary historically; the operational chat environment now runs principally on XMPP-based systems (CENTRIXS chat, Jabber-class servers) and various classified collaboration platforms, but the IRC acronym persists in some documentation. Context usually disambiguates: an IO planner means information-related capability; an SC officer talking about chat means the protocol.

The US Army's post-2018 approach to tactical network modernization, replacing the legacy WIN-T program with incrementally fielded "Capability Sets" of commercial-derivative tactical radios (PRC-158, PRC-163), mesh waveforms (TSM, SRW), small-form-factor SATCOM, and end-user devices — emphasizing affordability, simplicity, and survivability for large-scale combat operations.

"The current Army tactical network — Capability Sets, mesh waveforms, fielded brigade-by-brigade."

ITN is what replaced WIN-T as the Army's tactical network strategy — instead of one big program, a series of "Capability Sets" (CS21, CS23, CS25, CS27) that each ship a refined bundle of radios, waveforms, and end-user devices to brigades on a published cadence. The shift was philosophical: less custom hardware, more commercial-derivative; less dependence on stationary infrastructure; more mesh and software-defined waveforms. The actual ITN gear in a CS-fielded brigade is what soldiers carry day-to-day — PRC-158 manpacks, PRC-163 Leader Radios, TSM/SRW meshes, MUOS SATCOM access.

A United Nations specialized agency (International Telecommunications Union, headquartered in Geneva) responsible for coordinating global use of the radio-frequency spectrum, satellite orbits, and international telecommunications standards — issues binding Radio Regulations that allocate spectrum bands to specific services (broadcasting, mobile, maritime, aeronautical, satellite) on a regional and global basis.

"The UN body that allocates global radio spectrum and satellite orbital slots."

ITU is the United Nations agency that decides who gets to transmit on what frequency and which satellite orbital slot belongs to which country — and DoD spectrum managers, satellite operators, and electromagnetic-spectrum-operations planners spend significant effort coordinating US military spectrum use through the ITU framework. The Radio Regulations are not optional: when the Army wants to operate a radar at a particular frequency during an overseas deployment, when SDA wants to launch satellites into a particular orbit, when the Navy wants to operate maritime radio circuits in a particular band, the ITU framework governs what's permissible. The World Radiocommunication Conferences (WRCs) every four years are where the rules get rewritten, and DoD sends substantial delegations to defend US military spectrum allocations against commercial encroachment (5G in C-band being the high-profile recent example).

A US-developed UHF SATCOM waveform providing improved spectral efficiency over the legacy 25 kHz dedicated channels by supporting multiple users on a shared channel — historically the SATCOM waveform of choice on PRC-117G/PRC-152 and other HMS radios before the MUOS waveform became broadly available.

"The bridge UHF SATCOM waveform — multiple users on a shared channel."

IW (Integrated Waveform) is the SATCOM mode that made UHF SATCOM tolerable at scale — instead of one user per 25 kHz channel (the DAMA model), IW supports multiple users on a single allocated channel with adaptive coding and scheduling. IW is what most legacy SATCOM-equipped HMS radios run when they're on a UHF satellite. MUOS waveform is the next-generation replacement, but many formations still run IW because their assigned channels and terminals are IW-configured. Getting a SATCOM access plan and channel assignment from the J6 is a planning activity, not a self-service operation.

A joint fires planning and coordination system (joint automated deep operations coordination system) that provides automated tools for integrated fires planning across joint, multinational, and interagency partners — supports targeting workflow, fire support coordination measure management, airspace coordination, and the broader joint fires architecture — fielded as the standard fires-coordination tool across joint headquarters.

"The joint fires planning tool — targeting, FSCM management, airspace coordination."

JADOCS is the software the joint fires shop actually uses to do its work — targeting nominations, fire support coordination measures (FSCMs like coordinated fire lines and no-fire areas), airspace coordination with ATO and ACO inputs, and the broader workflow of getting effects on targets. Fires officers at division, corps, and joint task force headquarters learn JADOCS as part of their core kit; the system has been the standard joint fires-coordination tool for years, integrated with AFATDS on the Army artillery side and with the Theater Battle Management Core System (TBMCS) on the Air Force side. The system has the typical legacy-software quirks — it does the job, but the user experience reminds you that it was designed in an earlier era and has been incrementally modernized rather than rebuilt clean.

A joint logistics information system (joint asset movement management system) that supports tracking and movement coordination of unit equipment, personnel, and supplies during deployment, redeployment, and sustainment operations — interfaces with the broader Joint Deployment and Distribution Enterprise (JDDE) systems and supports US Transportation Command (USTRANSCOM) visibility into asset movement across the strategic mobility lanes.

"A joint logistics tracking tool — asset movement visibility across deployment lanes."

JAMMS is one of the tools in the Joint Deployment and Distribution Enterprise (JDDE) toolkit that USTRANSCOM and supported combatant commands use to track unit movement, equipment flow, and sustainment cargo as it moves through the strategic mobility lanes — air, sea, rail, and truck. For a unit deployment officer (UDO) or a transportation officer at a deploying brigade, JAMMS is one of the systems you're feeding data into for movement coordination, alongside JOPES, GATES, IBS, and the broader patchwork of joint logistics IT. The systems-of-systems problem in joint logistics IT is well-known — JAMMS is one piece of a fragmented landscape that DoD has been trying to rationalize for years.

A dedicated joint communications net (joint air request net) used by ground maneuver units to request immediate close air support and to coordinate immediate air mission tasking through the air request process — connects forward air controllers and joint terminal attack controllers (JTACs) with the air support operations center (ASOC) or air operations center for time-sensitive air request processing.

"The radio net for immediate air support requests — JTAC to ASOC for CAS calls."

JARN is the radio circuit a JTAC actually keys up on when there's troops in contact and a CAS request needs to go through right now — the immediate air request net that connects forward air controllers with the air support operations center (the ASOC, which sits at the corps level and handles immediate air requests for the ground force). The net has been around for decades in various forms; the modern implementation uses Link 16, secure voice, and digital text messaging in addition to traditional voice. For a JTAC in a fight, the JARN call is the moment where everything has to work — your radio, the ASOC bandwidth, the available aircraft, and the targeting data all have to come together in seconds. The institutional memory around JARN reaches back through every CAS war the joint force has fought.

The current US Army mission command terminal for mounted and dismounted forces, replacing the legacy FBCB2 system, providing friendly-force tracking (BFT integration), digital messaging (free-text and structured), mapping, fires integration, and limited C2 functions over L-band SATCOM and tactical-network data links.

"The current Army mission command terminal — replaced FBCB2."

JBC-P is the Army's current mission command terminal — the system soldiers actually use to send mission messages, see friendly positions, and integrate with fires and intel feeds. It replaced the legacy FBCB2 / FBCB2-BFT terminal that defined the Iraq-and-Afghanistan era. JBC-P runs on hardened vehicle and dismounted terminals; the user interface is functional rather than elegant, and "JBC-P keeps crashing" is a perennial training complaint. Despite the rough edges, JBC-P is the system that makes BFT and digital mission messaging actually work at the tactical edge.

The published joint-force document that assigns frequencies, call signs, suffixes, expanders, signal-operating instructions, and net structures for a specific operation or exercise — historically printed on a rotating wheel/pad, now typically distributed digitally — derived from the legacy Signal Operating Instructions (SOI) framework.

"The JCEOI — frequencies, call signs, and net structures for an operation."

JCEOI is the joint-force successor to the legacy SOI (Signal Operating Instructions) — the document that tells every radio operator in an operation what frequency to be on, what call sign to use, what suffix corresponds to which staff section, and how the net structure works. Historically distributed as a paper "wheel" that operators flipped to find the current day's assignments; modern distribution is via the J6/S6 staff in digital form. Losing the JCEOI is a serious operational security incident — it identifies friendly nets in clear text. Brigade S6 / J6 publishes the JCEOI; signal operators carry and protect it.

A USTRANSCOM-managed information system (Joint Capabilities Requirements Manager) that supported the validation and prioritization of joint capability requirements for strategic lift, mobility, and distribution — historically used by combatant commands to submit and track ISR, lift, and other mobility-supported requirements for joint requirements validation through the Joint Staff and USTRANSCOM processes.

"JCRM — USTRANSCOM system for managing and validating joint capability and mobility requirements."

JCRM is one of the USTRANSCOM-anchored systems for managing the validation and prioritization of joint capability requirements that ride on strategic lift and mobility — the ISR collection request that needs a U-2 or RQ-4 sortie allocated, the airlift requirement that has to compete in the joint prioritization process, the mobility-supported requirement that needs Joint Staff visibility. The system supports the back-office staff workflow of getting requirements into a format the Joint Requirements Oversight Council (JROC) and Joint Staff J-8 can act on. For most operators JCRM is invisible — they'll know that "the request is in JCRM" when their J3 staff officer mentions it, but they won't see the system itself. The DoD Dictionary entry is intentionally generic because the operational employment sits inside USTRANSCOM and Joint Staff workflows.

A J-7-managed application (Joint Doctrine Development Tool) that supports the drafting, staffing, coordination, and approval workflow for joint publications — provides the collaborative-authoring, comment-resolution, and version-control environment that joint doctrine lead agents and the broader coordination community use to develop and revise JPs.

"JDDT — J-7 application for collaborative drafting and staffing of joint publications."

JDDT is the application the J-7 stood up to replace the email-and-shared-drive workflow that joint doctrine development used to depend on — collaborative authoring environment, comment capture and resolution tracking, version control, and the workflow management that keeps a JP moving through its drafting, two-star coordination, and three-star approval phases. For a lead-agent doctrine writer working a joint publication, JDDT is the tool they use to draft the document, push it out for coordination, capture comments from every service and COCOM, resolve them, and shepherd the final version to approval. The tool reflects the institutional maturity of joint doctrine development as a coherent function rather than a series of ad-hoc projects.

A J-7-managed information system (Joint Doctrine, Education, and Training Electronic Information System) that provides access-controlled access to joint doctrine, joint professional military education materials, and joint training references — the principal authoritative repository for approved joint publications and related doctrinal materials.

"JDEIS — J-7 system providing access to joint doctrine, JPME materials, and training references."

JDEIS is the J-7-run system where the approved joint doctrine, the JPME courseware, and the joint training references live — for someone working at a CCMD or service headquarters with the right access, JDEIS is the authoritative source for the current version of any JP, the JPME curriculum materials supporting joint professional military education, and the joint training references that support joint exercise design. The system is access-controlled (not all materials are publicly releasable) but the publicly-releasable portion is mirrored on the open Joint Electronic Library. For a joint planner who needs to be sure they're looking at the current and authoritative version of a doctrine document, JDEIS is the source — not the random PDF that's been floating around the unit shared drive since 2018.

A joint information system (Joint Digital Information Gathering System) used in support of intelligence and operational collection workflows — provides digital collection, exploitation, and dissemination capability across joint intelligence elements — referenced in the DoD Dictionary as the labeled construct under the joint intelligence support framework.

"A joint digital collection system used in joint intelligence support workflows."

JDIGS is one of the labeled joint information-gathering systems carried in the DoD Dictionary — a digital collection and exploitation capability sitting inside the broader joint intelligence support architecture. For an analyst or collection-management staff officer, JDIGS shows up as one of the named tools in the joint collection ecosystem alongside JDISS, JWICS-hosted applications, and the COCOM-specific architectures. The DoD Dictionary entry is intentionally generic — the specific capabilities, accesses, and operational employment of JDIGS sit behind compartmentation and program-specific documentation, and aren't laid out in unclassified doctrine. For most service members the label is something you'd see in a system inventory, a J2 capabilities brief, or a collection-management staff product without seeing the system itself.

A joint information system (joint deployable intelligence support system) that provides deployable, multi-source intelligence access, analysis, and dissemination capability to joint task force commanders and subordinate elements — historically the principal deployable intelligence workstation for joint forces, now superseded in much of its function by web-enabled JWICS applications and the broader Distributed Common Ground System (DCGS) family.

"JDISS — the legacy deployable joint intel workstation, largely replaced by JWICS web apps."

JDISS is the legacy deployable joint intelligence workstation — the system that for years was the JTF J2's portable access to the multi-source intelligence picture, complete with analytical tools, message handling, and connection back into the broader intelligence enterprise. The system has been largely overtaken by the migration of intelligence applications onto JWICS-hosted web architectures (you don't need a JDISS-specific terminal if the application runs in a browser on any JWICS workstation) and by the service-specific Distributed Common Ground System architectures (DCGS-A, DCGS-N, DCGS-AF, etc.). For an experienced joint J2 staff officer, JDISS is a name they used in the 2000s and 2010s; for newer joint intelligence professionals, the function is delivered through different system labels but the underlying problem — deployable multi-source intelligence support — is the same.

The integrated network of tactical data links and supporting systems (joint data network) that exchanges machine-to-machine tactical data — primarily Link 16, Link 11, Link 22, Variable Message Format (VMF), and Situational Awareness Data Link (SADL) — across joint, coalition, and service component forces to build a common tactical picture for air, maritime, and ground operations.

"The joint data network — Link 16 and related tactical data links across the joint force."

JDN is the family of tactical data links that lets joint and coalition platforms see each other's picture in machine-to-machine time — Link 16 is the principal network (fighters, AWACS, AEGIS ships, Patriot batteries, JTACs), with Link 11 still in maritime use, Link 22 emerging as the Link 11 successor, VMF for ground-to-ground messaging, and SADL for some legacy applications. The JDN operations cell (JDNC) and JDN operations officer (JDNO) at a JTF or COCOM run the network: managing participation, deconflicting tracks, troubleshooting interoperability with coalition partners, and ensuring the common picture is actually common. For a tactical operator the JDN shows up as the symbology on the multi-function display, the SA call from the JTAC, the air-picture handoff from AWACS to the strike package.

A staff element (joint data network operations cell) at a JTF or COCOM that plans, coordinates, executes, and assesses tactical data link operations — manages network design, participation lists, network parameters, interoperability with coalition partners, and the day-to-day operational status of Link 16 and related JDN connectivity for joint operations.

"JDNC — the JTF/COCOM cell that runs Link 16 and tactical data link operations."

JDNC is the staff cell that actually makes the joint data network work — sitting in the J6 or J3 communications shop, owning the network design documents, publishing the participation lists, managing the Network Time Reference, troubleshooting why the Aegis cruiser and the F-15E aren't exchanging tracks the way they should. The work is part network engineer, part air-picture troubleshooter, part interoperability diplomat (the coalition partner's Link 16 terminal is configured slightly differently and the tracks aren't correlating). JDNC officers and senior NCOs are the ones who turn the data-link doctrine and tactical-publications-volume technical detail into a network that actually delivers shared situational awareness during a joint operation. The work product is invisible when it works and very visible when it doesn't.

A staff officer (joint data network operations officer) at a JTF, COCOM, or component headquarters who serves as the principal authority for tactical data link operations within that command — leads the JDN operations cell, signs off on network design and participation, and serves as the commander's expert on Link 16 and related JDN matters.

"JDNO — the joint staff officer responsible for Link 16 and tactical data link operations."

JDNO is the staff officer at the JTF or COCOM who owns tactical data link operations — typically an O-3 or O-4 with a deep background in either fighter-aviation Link 16 employment, naval combat-systems operations, or air defense Link 16 work. The JDNO leads the JDNC, signs off on the network design document for the operation, manages the participation list, and serves as the commander's subject-matter expert when Link 16 questions reach the J3 or J6 floor. The job is part operations officer, part communications engineer, part interoperability problem-solver. For a coalition operation, the JDNO is also the diplomat figuring out how to bring a partner-nation's data link terminal onto the network without breaking the existing picture. JDNOs come up through service-specific data-link career paths and get joint-qualified through experience.

A software application and management framework (joint enterprise network manager) used across DoD waveform-based tactical communications — particularly the SRW Soldier Radio Waveform and WNW Wideband Networking Waveform on JTRS-family radios — to plan, configure, monitor, and troubleshoot networked radio systems across a joint task force or coalition formation.

"The mission-planning and monitoring tool for SRW/WNW tactical radio networks."

JENM is the application that tactical S6 and J6 shops use to plan and manage the modern software-defined radio networks built on SRW and WNW waveforms — the JTRS-family Manpack, Rifleman, and HMS radios that replaced the legacy SINCGARS-only world. The planner builds the network configuration (channels, encryption, routing, neighbor tables), loads it to radios via fill devices or over-the-air management, and monitors the network in operation to identify which nodes are up, which are dropping, and where the topology is breaking. JENM is one of the unglamorous-but-essential tools that determines whether the platoon actually has comms when the maneuver starts; the difference between a working JENM plan and a broken one is the difference between a coordinated formation and radio silence.

A joint task force or joint force headquarters staff element (joint frequency management office) that plans, coordinates, and deconflicts electromagnetic spectrum use across the joint force — manages frequency assignments, host-nation spectrum coordination, deconfliction with civilian and partner-nation users, and the broader spectrum management piece of JEMSO — typically integrates with the JEMSOC and the J6.

"The joint frequency management shop — assignments, host-nation coordination, spectrum deconfliction."

JFMO is the joint frequency management shop — the staff that owns the spectrum assignment, host-nation coordination, civilian and partner-nation deconfliction, and the broader spectrum management piece of the JEMSO mission. For a unit S6/J6 trying to get a frequency for the satellite terminal, the radio net, the radar, or the EW system, the JFMO is who you go through. The work involves the host-nation regulatory authorities (every country owns its spectrum), the ITU international assignments, the joint restricted frequency list, and the deconfliction with civilian users (aviation, broadcast, cellular) whose lives don't stop because of the exercise or operation. The JFMO integrates closely with the JEMSOC where one exists; in smaller headquarters the JFMO and JEMSOC functions may be combined.

The officer designated to plan, coordinate, and manage the multi-tactical data link (Multi-TDL) network within a joint force area of operations — the JICO synchronizes Link 11, Link 16, Link 22, and related tactical data link operations across Service components to provide the joint force commander with an integrated common operational picture, coordinating frequencies, network roles, time-slot allocations, and interface management.

"The joint officer who owns the tactical data link network — Link 16, Link 11, Link 22 integration."

JICO is the officer who owns the joint tactical data link network — the Link 16 (and Link 11, Link 22, and successor) backbone that lets an E-3 Sentry, an F-35, an Aegis destroyer, a Patriot battery, and a JSTARS all see the same air picture in near-real-time. For a JICO, the daily work is the Operational Tasking Data Link (OPTASK Link) — the message that specifies the network architecture, role assignments, frequency plan, and time-slot allocations for the joint force's data links — plus continuous coordination across Service components when networks need adjustment, when participating units join or leave, or when interoperability issues surface. JICO is one of those joint billets where one person's technical competence has outsized operational consequences across the entire COP.

A Department of Defense information environment that supports the exchange of operational, intelligence, and administrative information across joint, combined, and interagency boundaries — the JIEE encompasses the networks, services, and information-management practices that enable joint information sharing, and is part of the broader DoD Information Network (DODIN).

"The joint information-sharing environment — networks and services for cross-component, cross-agency, cross-coalition info exchange."

JIEE is the umbrella term for the joint information-sharing environment — the networks, services, data standards, and information-management practices that let a Service component share operational and intelligence information with another Service component, with a coalition partner, with an interagency partner, or with a higher headquarters. In practice, JIEE shows up in operational life as the SIPRNet and the coalition networks (CENTRIXS variants), the cross-domain solutions that move data between classification levels, and the information-management policies that govern what can be released to whom. For a J-6 communicator or a J-2 intel manager, JIEE is the policy and infrastructure backdrop against which day-to-day information-sharing decisions get made.

Per the DoD Dictionary, the Joint Worldwide Intelligence Communications System — the DoD top-secret/sensitive compartmented information (TS/SCI) global communications network providing voice, video, and data services to the intelligence community and joint force at the TS/SCI level, commonly referenced under the more familiar acronym JWICS.

"The TS/SCI joint network — JWICS by another name in DoD Dictionary form."

JMICS is the formal DoD Dictionary entry for what everyone in uniform calls JWICS — the top-secret/sensitive compartmented information network where the intelligence enterprise actually lives. SIPR holds you at SECRET; JWICS (JMICS) is where the TS/SCI traffic, the imagery products, the SIGINT reporting, and the compartmented programs sit. To touch JMICS you need a TS/SCI clearance, billet justification, a hard-wall SCIF, and a specific account. The terminal sits in a SCIF, not at your desk; you don't take notes home from it; the screensaver tells you what classification you're working at. Operationally it's the network where joint intel briefings happen, target development gets staffed, and the J-2 picture gets built. Most service members go a full career without an account; the ones who get one usually wish they hadn't the first time the rules about handling get briefed.

Per the DoD Dictionary, the Joint Mission Planning System — the DoD joint mission planning software environment used by aviation units across the Services to plan combat and support missions, integrating route planning, weapons-target pairing, threat assessment, fuel and time-on-target calculations, and digital transfer of mission data to aircraft mission systems.

"The joint aviation mission planning software — replaces a paper era of mission planning."

JMPS is the joint software environment aircrews use to plan missions — the descendant of and replacement for a generation of Service-specific mission planning tools (Air Force PFPS, Navy TAMPS, etc.). The system handles route planning against terrain and threat overlays, weapons-target pairing inputs that pull from JMEM-derived weaponeering, time-on-target and fuel calculations, contingency routes, and the digital export to cartridge or data-link load that the cockpit mission computer reads at start-up. Aircrew planning is now hours of clicking through JMPS rather than the old days of paper TPCs and grease pencils — which is mostly an improvement but means a JMPS outage shuts down mission planning until it's back. JMPS is fielded across fixed-wing and rotary-wing communities; the workflow varies by airframe Mission Planning Environment (MPE) module.

Per the DoD Dictionary, a joint network operations control center — the joint force command and control element responsible for operating, monitoring, defending, and managing the joint force's communications networks, including coordination with Service component network operations centers, the Defense Information Systems Agency (DISA), and US Cyber Command (USCYBERCOM) for network defense.

"The joint network ops center — runs and defends the joint force's comms networks."

JNCC is the joint version of the network operations center every Service runs — the cell that keeps NIPR, SIPR, JWICS, voice, video, and the operational data services running across the joint force, monitors for outages and intrusions, and coordinates with DISA and CYBERCOM when something is more than a routine outage. The work is part everyday network admin (a circuit went down between this SCIF and that one), part incident response (something is scanning the perimeter), part operational planning (the J-6 needs networks lit at the new forward operating base by H+96). JNCC personnel are usually a mix of joint network operations 25/2T0/IT/0651-coded service members plus DISA civilians and contractors. In a major operation, the JNCC is busier than most desks on the joint staff and gets less recognition than any of them.

Joint Photographic Experts Group (JPEG) is the international standards body (formally ISO/IEC JTC 1/SC 29/WG 1 in coordination with ITU-T) that produces the JPEG family of image compression standards used throughout DoD imagery, GEOINT, and routine office workflows — the JPEG standard itself (ISO/IEC 10918) is the most widely deployed lossy still-image compression format in existence.

"The JPEG standards body — the image compression format everybody uses."

JPEG shows up in the DoD Dictionary because the file format is the universal currency of imagery in joint operations — the .jpg attachment on every SITREP, the format the UAS feed compresses to before it crosses the bandwidth-constrained tactical network, the format the briefing slide imagery saves to. The acronym is technically the international standards body (a joint ISO/IEC/ITU group), but in everyday usage it just means the file format. For a service member, the only practical concern is that JPEG is lossy compression — every save degrades the image slightly, so source imagery should be preserved in original format and only converted to JPEG for distribution. Classified imagery handling rules apply to JPEG files like any other.

A time and geographically-oriented listing of TABOO, PROTECTED, and GUARDED functions, nets, and frequencies, limited to the minimum necessary to enable friendly forces to use the electromagnetic spectrum without unacceptable interference (DoD Dictionary, November 2021).

"The JRFL — a list of friendly frequencies you do not jam."

JRFL is the document that keeps your electronic attack from shooting your own communications in the back — a curated list of frequencies the joint force has flagged as TABOO (never engage), PROTECTED (friendly use, jam only if mission-essential), or GUARDED (adversary use you want to exploit, not destroy). The J6 spectrum manager and the EW staff build and maintain it together. The JRFL is intentionally kept as short as possible because every frequency on it constrains friendly EW employment. Cyber/EW operators who break the JRFL — jamming a TABOO frequency by accident — get a stern conversation with the J6 and the JFC.

The process and program for identifying, characterizing, and resolving electromagnetic interference incidents that affect joint operations, providing standardized reporting, technical analysis, and resolution coordination across Services and combatant commands through the Joint Spectrum Center and Service spectrum management offices (DoD Dictionary, November 2021).

"JSIR — the joint process for reporting and resolving spectrum interference."

JSIR is the standardized way the joint force reports, analyzes, and resolves electromagnetic interference incidents — when a SATCOM downlink starts taking hits, when a GPS receiver loses lock at a specific location, when a radar develops a mystery noise floor. The user fills out a JSIR report (the form has been around for decades and has its own quirks), the Service spectrum office routes it to the Joint Spectrum Center for analysis, and the resolution chain works the problem — which can mean tracking down a friendly emitter on the wrong frequency, identifying intentional adversary jamming, or finding a faulty piece of friendly equipment. JSIR is one of the unglamorous joint processes that keeps the EM spectrum usable; experienced operators learn to file good JSIRs because bad ones don't get traction.

The joint force element responsible for planning, coordinating, and executing electromagnetic spectrum management in support of a joint force commander, providing frequency assignment, interference resolution coordination, JRFL development, and spectrum supportability across the joint operations area (DoD Dictionary, November 2021).

"JSME — the JFC's spectrum management shop inside the J6."

JSME is the J6 sub-element that does the day-to-day work of keeping the electromagnetic spectrum usable for a joint force — it assigns frequencies to Service components, builds and maintains the JRFL, coordinates host-nation spectrum approvals, runs interference resolution through the JSIR process, and synchronizes spectrum with EW employment. For a J6 watchstander, the JSME is the corner of the watchfloor where the spectrum chart lives and where the frequency assignment requests pile up. The JSME also interfaces with the Joint Spectrum Center (DISA) for technical analysis support and with national spectrum authorities for civilian-spectrum deconfliction. Without a functioning JSME, joint comms degrade into a self-jamming mess inside the first 72 hours.

The Department of Defense top-secret/SCI network, operated by DIA, used by the intelligence and special-operations communities for compartmented intelligence sharing.

"The high-side intelligence network used across the joint force."

JWICS lives inside SCIFs. Access requires TS/SCI eligibility and a read-in to whatever compartments your job needs. Most service members never touch it directly; the intelligence products from JWICS get sanitized down and pushed onto SIPR or NIPR as releasable summaries. When someone says "the high side," they usually mean SIPR — JWICS is the higher-high side most people just hear about.

A computer network that interconnects computers, servers, and devices within a limited geographic area such as an office, building, or campus, providing local data communications and access to shared resources — within DoD contexts, typically referring to an installation, headquarters, or shipboard data network (DoD Dictionary, November 2021).

"LAN — the local network at a building, installation, or ship."

LAN is the generic IT vocabulary for the local network inside a building, installation, or ship — NIPRNET LAN, SIPRNET LAN, JWICS LAN, or a Service-specific tactical network depending on classification and purpose. The DoD Dictionary captures it because joint communications and IT doctrine reference it as the basic unit of installation-level connectivity. For the soldier or sailor, LAN is just "the network" — the thing that lets you get to email, SharePoint, the local printer, and whatever applications the command has on its servers. The S-6 or J-6 owns LAN operations and security; the user gets a CAC-enabled login and is told not to plug in unauthorized devices. LAN outages are the universal annoyance.

The standardized tactical data link used by the US and allied forces for the secure, jam-resistant exchange of digital tactical information between airborne, surface, and subsurface command, control, and weapons platforms.

"The joint tactical data link used for secure exchange of tactical information."

Link 16 is the joint TDL: fighter aircraft, AWACS, ground command posts, naval ships, and air-defense systems exchange a common tactical picture in near real time. The MIDS (Multifunctional Information Distribution System) terminal is the radio that carries the Link 16 waveform; the NATO STANAG 5516 standard defines the message formats. Crewed and uncrewed platforms operate together on Link 16 in modern joint operations; managing the Link 16 network (J3 air ops, the joint interface control officer) is its own specialty.

The Marine Corps system of facilities, equipment, communications, procedures, and personnel through which the aviation combat element of a Marine Air-Ground Task Force commands and controls aviation operations — comprising the Tactical Air Command Center, the Tactical Air Operations Center, the Direct Air Support Center, the Air Defense Communications Platoon, and Marine Air Control Squadrons (DoD Dictionary, November 2021).

"MACCS — the Marine air C2 system that ties together TACC, TAOC, DASC, and MACS."

MACCS is the connected web of Marine air command and control that lets a Marine Air-Ground Task Force run its own aviation combat element without depending on the joint force air component for tactical control. The Tactical Air Command Center is the senior node where the ACE commander runs the aviation fight; the Tactical Air Operations Center handles airspace and air defense; the Direct Air Support Center pushes CAS to the ground combat element; the Marine Air Control Squadrons provide the radar and surveillance. The architecture is unique to the Marine Corps because the MAGTF model depends on integrated air-ground operations, which depends on a C2 system the ACE controls. Inside a joint air operation, MACCS plugs into the JFACC structure but retains the internal MAGTF coordination function. The doctrine sits in MCWP 3-25.

A Department of Defense-sponsored program in which licensed amateur radio operators provide auxiliary and emergency communications for the military, particularly during emergencies and contingencies, and provide morale support communications for deployed service members and their families.

"A DoD program using amateur radio operators for auxiliary military comms."

MARS is one of those quietly important programs — civilian volunteer radio operators, separately licensed by DoD and by the FCC for amateur radio, providing backup and overflow communications when primary systems fail. Members handle morale traffic for deployed personnel, support emergency communications during disasters, and exercise the kind of HF radio skills that become important when satellite links go down. Army MARS, Navy/Marine MARS, and Air Force MARS each operate their own branches.

The Department of Defense board that coordinates communications-electronics policy, standards, and interoperability across the Services, combatant commands, and defense agencies — chartered to support joint and combined interoperability through standardization of communications-electronics systems and procedures (DoD Dictionary, November 2021).

"The MC4EB — DoD board coordinating comms-electronics policy and interoperability."

MC4EB is the DoD-level board where communications-electronics policy, standards, and interoperability issues get coordinated across the Services and combatant commands — the institutional mechanism for keeping Army, Navy, Air Force, Marine Corps, Space Force, Coast Guard, and defense agency comms-electronics decisions from drifting in incompatible directions. The board sits inside the broader joint C4 governance architecture under the Joint Staff J6 and DoD CIO. Operationally, MC4EB is the kind of forum that adjudicates whether a new Service-specific waveform gets joint-interoperability waivers, whether a frequency allocation crosses Service lines, or whether a communications standards conflict gets resolved one way or the other. The acronym is one of the older joint C4 institutional names; the function has evolved across reorganizations but the coordination need has not.

Per the DoD Dictionary of Military and Associated Terms (November 2021), the discipline of integrating communications systems, networks, and procedures across multinational forces to enable command and control, intelligence sharing, and operational coordination among coalition partners — addresses both the technical interoperability and the procedural standardization required for multinational operations.

"Multinational communications integration — making coalition comms actually talk to each other."

MCI is the discipline that turns "coalition operations" from a slide-deck phrase into actual radios, networks, and chat rooms that allied partners can use to talk to each other in real time. The technical side is hard (different cryptographic standards, different frequency plans, different network protocols, different security classifications) and the procedural side is harder (who can see what, on what release authority, on whose network). NATO operations have driven decades of MCI work through STANAGs and the NATO Federated Mission Networking program; coalition operations outside NATO (Five Eyes, ad hoc coalitions) tend to be done with mission-specific releasability agreements. For a J6 communications planner, MCI is one of the most consequential and most thankless parts of the job.

Per the DoD Dictionary of Military and Associated Terms (November 2021), the standardized maritime report format used by mine countermeasures forces to report mine countermeasures activity — including suspected mine contacts, identified mines, mine disposal actions, and the status of swept and cleared areas — typically transmitted via Allied Tactical Publication formats to the supported maritime commander.

"The standardized mine countermeasures report — what MCM forces send up after each evolution."

MCMREP is the standardized report format that mine countermeasures forces use to send tactical reporting up to the supported maritime commander after each MCM evolution — what was swept, what was found, what was disposed of, and what areas can now be characterized as cleared. The format matters because MCM reporting feeds the broader Q-route management and threat picture; ambiguity here gets ships sunk. The MCMREP, like other maritime tactical reports, lives inside the Allied Tactical Publication system that NATO and US Navy forces use jointly, so the format is interoperable with allied MCM forces operating in the same area. Mine warfare officers and MCM ship operations specialists are the ones who actually generate MCMREPs.

The constellation of military and government satellites providing communications for the Department of Defense and other federal users, including narrowband (UFO/MUOS), wideband (WGS), and protected (Milstar/AEHF) tactical and strategic communications.

"The constellation of military communications satellites."

MILSATCOM is the umbrella term covering the layered DoD satellite communications architecture: narrowband UHF for tactical voice/data through UFO (legacy) and MUOS (current), wideband for higher-throughput general-purpose comms through WGS, and the protected anti-jam, low-probability-of-intercept layer through Milstar (legacy) and AEHF (current). Most service members interact with MILSATCOM through the radios on their vehicle or aircraft without thinking about which constellation is carrying their traffic.

The legacy DoD protected satellite communications constellation, providing anti-jam, low-probability-of-intercept, and low-probability-of-detection communications at extremely high frequency (EHF) for nuclear and tactical users, now being augmented and replaced by the AEHF constellation.

"The DoD legacy protected EHF satellite communications system."

Milstar entered service in the mid-1990s with a small constellation of geosynchronous satellites providing protected EHF communications. Its primary mission has always been the protected (anti-jam, LPI/LPD) layer that strategic forces need to remain commandable through electromagnetic warfare attempts to suppress comms. AEHF is the modern follow-on with greater capacity; Milstar satellites remain operational alongside AEHF as the architecture transitions.

Per the DoD Dictionary of Military and Associated Terms (November 2021), MNL has two distinct meanings: a master net list (the comprehensive list of communications nets for a command, used in communications planning) and multinational logistics (the discipline of providing logistic support across contributing nations of a multinational force).

"MNL — master net list (comms planning) or multinational logistics (coalition logistics)."

MNL is one of the dual-use acronyms the DoD Dictionary carries because both meanings show up in operational documents. The master net list meaning is communications planning — the comprehensive list of every radio net, encryption family, and frequency assignment for a command, owned by the J6 communications staff and the document a new signal officer reads on day one of an assignment. The multinational logistics meaning is the discipline that JP 4-08 codifies — providing logistic support across contributing nations of a multinational force through lead nation arrangements, acquisition and cross-servicing agreements, host nation support, and the coordination centers (MJLC, MNJLC, MNLC) that the joint doctrine has built out. Context disambiguates which MNL is meant; in a comms order it is the net list, in a logistics order it is the discipline.

Per the DoD Dictionary of Military and Associated Terms (November 2021), an integrated network combining multiple tactical data links (such as Link 16, Link 11, Link 22, and variable message format) to enable the exchange of tactical data among participants operating different link standards within a single coherent picture.

"A multi-tactical data link network — bridges Link 16, Link 11, and other TDLs into one picture."

MTN is what makes a joint air picture actually joint — the bridging layer that lets a Link 16-equipped fighter, a Link 11-equipped ship, and a variable message format-equipped ground unit see each other and exchange targeting and identification data despite running different underlying tactical data link standards. The translation happens through forwarder nodes (often on E-3, E-7, or shipboard systems) that re-encode messages across link standards. For the operator this is mostly invisible until it breaks — at which point the fighter on Link 16 stops seeing the ship's air defense picture, and the air boss is suddenly making decisions with half the data. MTN configuration is one of the quietly hardest parts of any large joint exercise.

The US Navy-managed narrowband SATCOM constellation providing UHF tactical SATCOM services to mobile users across the joint force, operating with a WCDMA-based waveform that supports simultaneous multi-user access and significantly higher capacity than the legacy UFO constellation — the successor narrowband SATCOM system.

"The narrowband SATCOM constellation tactical radios call into."

MUOS is the satellite constellation a modern PRC-117G or PRC-158 talks to when it runs UHF SATCOM in the MUOS waveform — a Navy-built, Navy-operated system that replaced the legacy UFO (UHF Follow-On) constellation. MUOS gives mobile tactical users (manpack radios, vehicles, aircraft) reliable narrowband voice and data beyond line of sight without needing the high-end terminals that wideband SATCOM (WGS, AEHF) requires. MUOS access is controlled and prioritized; getting an MUOS slot for an exercise is a planning activity, not a casual decision. The constellation went fully operational in the 2020s.

Per the DoD Dictionary of Military and Associated Terms (November 2021), the Naval Satellite Operations Center — the Navy command at Naval Base Ventura County, Point Mugu, California responsible for command and control of Navy-owned communications satellites and supporting payloads, including the Mobile User Objective System (MUOS) and legacy UFO/FLTSATCOM systems.

"NAVSOC — Point Mugu satellite operations center for Navy communications satellites including MUOS."

NAVSOC is the Navy's satellite operations center at Naval Base Ventura County (Point Mugu), California — the command that flies and operates the Navy-owned communications satellites and supporting payloads. The principal current constellation is the Mobile User Objective System (MUOS), the geosynchronous narrowband communications system that gives deployed users beyond-line-of-sight voice and data on small terminals; legacy UFO and FLTSATCOM payloads are still in the picture in residual form. With the Space Force taking custody of much of the broader DoD space mission, NAVSOC remains a Navy-retained satellite operations capability because of the close coupling between MUOS and Navy/Marine end-users. The slug bare-name covers this; the dictionary entry truncation "naval special" is a separate-meaning artifact resolved by the NAVSOF entry.

Per the DoD Dictionary of Military and Associated Terms (November 2021), Net-Centric Enterprise Services — the DISA-managed portfolio of enterprise-level information services (collaboration, messaging, content discovery, service management) that provide common, interoperable services to DoD users across the Global Information Grid; largely subsumed under current Joint Information Environment and DoD Enterprise Cloud constructs.

"NCES — the DISA enterprise services portfolio (collab, messaging, discovery) under the JIE construct."

NCES is the DISA-managed portfolio of common enterprise services that was supposed to give the joint force a single set of interoperable collaboration, messaging, discovery, and service-management tools across the Global Information Grid. In practice the NCES catalogue showed up to most users as Defense Collaboration Services, the DoD-wide messaging tools, and the back-end services that other applications depended on. Much of the construct has been subsumed under the broader Joint Information Environment (JIE) and Joint Warfighting Cloud Capability (JWCC) initiatives, but the NCES vocabulary persists in DISA service catalogues and in older capability documents. The term is most useful as a way to look up the historical service catalogue when reading older DoD IT documentation.

Per the DoD Dictionary of Military and Associated Terms (November 2021), a national-level conference line established to facilitate communications among federal, state, and local response organizations during major incidents and emergencies, coordinated under the National Incident Management System framework.

"The National Incident Communications Conference Line — interagency phone bridge for major incident coordination."

NICCL is the standing federal interagency conference bridge that gets activated during major domestic incidents — hurricanes, wildfires, terrorist incidents, large-scale industrial accidents — to give DHS/FEMA, the affected state and local authorities, supporting federal departments, and any military Defense Support of Civil Authorities element a single coordination line for time-sensitive coordination. The bridge is run under the NIMS framework and typically managed out of the FEMA National Response Coordination Center. For a USNORTHCOM or DCO-DS planner the NICCL is one of the lines that needs to be on during a developing event because it is where the civilian incident commanders and the federal partners are actually talking. The mechanism sounds bureaucratic; it is what keeps an incident response from devolving into a hundred parallel phone calls and contradictory direction.

The unclassified data network operated for the Department of Defense, used to exchange Sensitive But Unclassified information and to access the public internet through controlled gateways.

"The DoD's secure network for routine, unclassified business."

NIPR is what most service members spend the day on — a corporate-feeling intranet with CAC login, mandatory training modules, and a web filter that blocks roughly anything interesting. It is unclassified, but it is still a DoD system: monitoring is constant and the user agreement you click past every morning says so. Outages bring everything to a halt because pay, personnel, supply, email, and training all live here.

Per the DoD Dictionary of Military and Associated Terms (November 2021), the Department of Defense unclassified network providing IP-based connectivity for unclassified email, web access, and applications across DoD organizations, interconnected to the public internet through controlled boundary defenses.

"NIPRNET — the DoD unclassified network that runs daily email, web, and applications."

NIPRNET is the DoD unclassified network — the layer where day-to-day work happens for most service members and DoD civilians: Outlook email, milSuite, the public-facing web, training systems, the bulk of administrative applications. It connects to the public internet through controlled boundaries (the Joint Regional Security Stacks, increasingly the Thunderdome zero-trust architecture). NIPRNET is the network most users interact with consciously, and the one they curse most often because of bandwidth caps, security stack latency, and the periodic outages that come with running a large enterprise network behind boundary defenses. SIPRNET (secret) and JWICS (top secret/SCI) are the classified peers; CAC plus PIV authentication gates everything. For most of the joint force, "the network is slow" almost always means NIPRNET specifically.

Per the DoD Dictionary of Military and Associated Terms (November 2021), the standard file format used by the US Department of Defense and the intelligence community for the transmission, storage, and exchange of imagery and imagery-related products across systems and organizations.

"NITF — the standard imagery file format DoD and the IC use to exchange imagery products."

NITF is the standard file format for imagery and imagery products across DoD and the IC — a container format (NITF 2.0, 2.1, NSIF) that holds the imagery itself plus metadata (sensor type, geolocation, classification markings, target identifiers, annotations) in a way that imagery exploitation systems, GIS applications, and the broader GEOINT enterprise can all read. For a GEOINT analyst at NGA or in a COCOM intelligence directorate, NITF files are the daily working unit — the image plus all the context that makes it usable for targeting, analysis, or mission planning. The format is one of the boring-but-load-bearing standards that lets a satellite collection feed into an exploitation tool feed into a targeting product without losing the metadata along the way. STANAG 4545 mirrors NITF for NATO interoperability.

Per the DoD Dictionary of Military and Associated Terms (November 2021), the joint Navy and Marine Corps office responsible for electromagnetic spectrum management, including frequency assignment, host-nation coordination, spectrum supportability, and spectrum policy across Navy and Marine Corps systems and operations.

"Navy and Marine Corps Spectrum Office — joint Navy/Marines spectrum management and host-nation coordination."

NMCSO is the joint spectrum management office for Navy and Marine Corps — the entity that does frequency assignment, host-nation coordination for spectrum use overseas, and spectrum supportability assessments for new Navy and Marine systems. For a program manager fielding a new radar, radio, jammer, or unmanned system, NMCSO is one of the gates that has to be passed: does the system have a clear path to operate in the frequencies it needs, in the geographies it needs to operate in, without conflicting with civilian or partner-nation users? The office works alongside the broader DoD Chief Information Officer spectrum enterprise and the National Telecommunications and Information Administration (NTIA) on the civilian side. The work is invisible until a deploying ship or MAGTF needs spectrum clearance in a host nation and the answer suddenly determines whether their equipment can be turned on at all.

A communications planning model that designates four prioritized methods of communication for each task or relationship: primary (preferred), alternate (backup), contingency (degraded conditions), emergency (last resort).

"PACE planning ensures units stay connected even when primary comms fail."

PACE is one of the most portable concepts in military planning. It works for any plan that depends on talking to anyone — convoy ops, family communications during deployment, even your CAO contact list if you become a casualty. Brief it. Test it. Most "the radios stopped working" stories trace to a PACE plan that was written but never rehearsed.

The Harris/L3Harris multiband multi-mission manpack radio operating across HF, VHF, UHF, and SATCOM ranges (30 MHz - 2 GHz), running SINCGARS, ANW2, HAVEQUICK, SATCOM, and other waveforms — the workhorse multi-mission manpack of the late-OEF/OIF era and follow-on operations, widely fielded across the joint force.

"The multi-band manpack that became the SOF-and-conventional standard."

PRC-117G is the radio that made multi-band capability ordinary — a single manpack that could run SINCGARS to talk to the platoon, ANW2 to mesh with adjacent units, and UHF SATCOM to reach higher. It was the radio SOF formations carried first and conventional formations adopted broadly after Iraq/Afghanistan demonstrated the value. Heavier than a SINCGARS ASIP (a 117G with batteries, fills, and an antenna kit is genuinely heavy), but it replaces multiple radios with one. The 117G is being supplemented by the newer 158 in many formations — but the 117G remains widely fielded and trained.

The Thales handheld multiband multi-mission radio operating 30 MHz - 512 MHz (MBITR original; the JEM variant extends to higher bands), the joint inter/intra-team radio fielded broadly across the joint force as a small handheld voice/data radio with SINCGARS and other waveform support — the historical small-team radio that preceded the broader HMS handheld family.

"The handheld MBITR — the small radio every SOF team carried."

PRC-148 was the radio that taught the joint force what a tactical handheld could do — the Thales MBITR (Multiband Inter/Intra Team Radio) became the SOF handheld of choice in the early 2000s and got broadly fielded across conventional formations after that. The JEM (Joint Enhanced MBITR) variant extended the band coverage. The 148 is being supplemented by the newer PRC-152, PRC-163, and similar handhelds — but tens of thousands of 148s are still in inventory, and the form factor (chest-mounted handheld with PTT cable to a headset) is the form factor most modern radios mimic.

The Harris/L3Harris multiband handheld multi-mission radio operating 30 MHz - 512 MHz, running SINCGARS, HAVEQUICK, and other waveforms, fielded as the joint handheld counterpart to the PRC-117G manpack — the workhorse handheld of the late-OEF/OIF era and follow-on operations.

"The 117G's handheld sibling — same family, smaller package."

PRC-152 is the handheld that pairs with the 117G manpack — same vendor lineage, similar waveform support, much smaller form factor. The 152 is what a squad leader carries on their chest while the manpack 117G is in the platoon HQ rucksack or vehicle. The 152 has its own challenges (battery life under heavy duty cycle is the perennial complaint), but it is the radio that broadly democratized multi-band capability down to the squad-leader level. The newer PRC-163 is its successor for two-channel operation.

The Collins Aerospace/L3Harris two-channel multiband manpack radio, the next-generation joint manpack designed to run two waveforms simultaneously (typically a combat-net waveform and a SATCOM or mesh waveform) — the manpack component of the Integrated Tactical Network (ITN) capability sets.

"The two-channel manpack — runs combat-net and SATCOM simultaneously."

PRC-158 is what the next decade of Army tactical communications is being built around — a two-channel manpack that can run, for example, a SINCGARS combat-net AND a UHF SATCOM uplink at the same time on the same radio. That capability matters: the legacy approach required two radios (and two operators) to do what the 158 can do alone. Fielding is incremental — the radio shows up in ITN Capability Set fielding tranches, brigade by brigade — and the early variants had teething problems. But the 158 is the manpack the modern combat-net architecture assumes.

The L3Harris HF/VHF multi-mission manpack radio operating 1.5 MHz - 60 MHz (HF and lower-VHF), designed to provide beyond-line-of-sight HF communications without satellite dependency — fielded across SOF, conventional, and joint formations as the modern HF replacement for legacy HF systems.

"The HF manpack — the radio that talks long-distance without satellites."

PRC-160 is the radio that brought modern HF capability back to the tactical formation — HF is the band that bounces off the ionosphere and lets a manpack talk hundreds or thousands of kilometers without a satellite. After two decades of relying heavily on SATCOM, the joint force has rediscovered HF as a SATCOM-denial backup and an alternative path. The 160 makes HF practical for tactical operators (automatic link establishment, wideband data modes) in ways the legacy AN/PRC-104 and AN/PRC-150 couldn't. SOF formations adopted it first; conventional formations are following. HF discipline (propagation prediction, antenna selection) is a skill being rebuilt across the force.

The L3Harris two-channel multiband handheld radio, the next-generation joint handheld designed to run two waveforms simultaneously — the handheld counterpart to the PRC-158 manpack and the "Leader Radio" component of the Integrated Tactical Network (ITN) capability sets, typically issued to squad and platoon leaders.

"The Leader Radio — the squad-leader's two-channel handheld."

PRC-163 is the "Leader Radio" of the modern Integrated Tactical Network — the handheld that lets a squad leader simultaneously talk on the platoon combat net AND participate in a mesh-data network (SRW or TSM) without swapping radios. Two-channel handheld is the technical step the 152 couldn't take; the 163 fills that gap. As with the 158, fielding is incremental by ITN Capability Set; the radio shows up to formations on a published schedule. The 163 is the radio a modern infantry leader actually carries when their formation has been ITN-fielded.

The US Army/Marine Corps Vietnam-era VHF FM manpack radio operating 30-75.95 MHz, replaced by SINCGARS beginning in the late 1980s — still occasionally referenced in legacy doctrine and historical training materials as the conceptual ancestor of modern combat-net radios.

"The Vietnam-era manpack — the radio whose voice you hear on every war movie."

PRC-77 is the radio that gave a generation of soldiers their idea of what a tactical radio looks like — the green brick with a long whip antenna and a handset, carried by the company RTO. It is functionally obsolete; the last operational PRC-77 fills were retired decades ago. But the radio still appears in training materials, museum displays, and the institutional memory — "Prick-77" was the way platoons talked from the late 1960s through the 1980s, and many of the conventions of tactical communications (CFF brevity, MEDEVAC 9-line, contact reports) were forged on it. If someone says "back in my day we had Prick-77s," they're telling you when they served.

The US Army family of VHF combat-net radios operating in the 30-87.975 MHz range with single-channel and frequency-hopping modes, including the manpack (RT-1523 family), vehicular (RT-1439 and successors), and airborne configurations — the legacy backbone of squad/platoon/company/battalion combat-net communications since the late 1980s, gradually being replaced by HMS-family multiband radios but still widely fielded.

"The Army's combat-net radio — the family that lets a squad talk to its leader."

SINCGARS is the radio almost every soldier has touched — green, RT-1523 manpack or vehicular variant, the family that has carried "I'm black on water, send recovery" and "TIC on grid 12345 67890" since the late 1980s. Single-channel mode runs a fixed frequency; frequency-hopping mode (the security feature) cycles through hundreds of frequencies per second from a loaded hopset. Loading hopsets, time-of-day, and ECCM data correctly is a perennial maintenance burden — a single radio with bad fill talks to no one. The HMS family (PRC-117G, PRC-158) is gradually replacing SINCGARS for primary combat-net duty, but SINCGARS remains in active inventory and in many vehicle racks.

The classified data network operated for the Department of Defense to handle information up to and including SECRET, physically and logically separated from NIPR.

"The classified network used for sensitive operational planning."

SIPR is a different physical computer in a different controlled space, with separate cabling, separate accounts, and a separate culture of "do not screw this up." Browsing is slower, the tools are fewer, and there is no streaming media. The biggest practical risk is spillage — moving classified info onto NIPR by accident — which triggers a multi-week sanitization and incident-report cycle and a counseling that lives in your file.

A US Army-developed software-defined mobile ad-hoc networking (MANET) waveform designed for small-unit voice and data networking, operating in the UHF and L-band ranges, providing self-forming and self-healing mesh networks for squad/platoon/company-level tactical communications — historically tied to the legacy JTRS handheld program and the Rifleman Radio.

"The original Army-developed mesh waveform for small-unit nets."

SRW is the waveform you'll see on older HMS-family radios and on the legacy Rifleman Radio — a mesh waveform that lets handhelds form a self-healing network without infrastructure. The waveform predates TSM (Trellisware) and ANW2 (Harris) in the Army's mesh evolution, and it was the early flagship for the now-defunct JTRS program. SRW remains in service on many fielded radios; newer ITN Capability Sets have shifted emphasis to TSM. If two radios "mesh" via SRW, they form a local network without higher-level infrastructure — a key capability for squad-and-below tactical operations.

A SpaceX-operated military and government communications service derived from the commercial Starlink LEO constellation, with hardened terminals, encrypted communications, and contracts with multiple US government customers (USSF, NRO, Pentagon offices) for both communications and (under separately disclosed contracts) Earth-observation payload hosting — emerged 2022-2024 as a major shift in the commercial-military communications landscape.

"The SpaceX military-grade variant of Starlink — encrypted, hardened, classified contracts."

Starshield is the military variant of Starlink — same constellation lineage, hardened terminals, encrypted communications, and contracts the public knows about (USSF anti-jam terminals) plus contracts the public doesn't fully know about (NRO Earth-observation payload hosting). The service emerged in 2022-2024 as one of the more consequential shifts in the commercial-military space relationship: a major commercial space company providing services across the classified-to-unclassified spectrum at a scale and pace traditional military SATCOM programs have struggled to match. The implications for traditional MILSATCOM program structures (AEHF, WGS, MUOS) are still being worked through; Starshield doesn't replace dedicated military comms, but it changes what the broader portfolio looks like.

A family of General Dynamics-built High Assurance Internet Protocol Encryptor (HAIPE) devices providing NSA-certified Type 1 IP-layer encryption for tactical and enterprise networks — including the KG-175D, KG-175G, and KG-175N variants — the standard inline network encryptor for classified IP traffic across the DoD.

"The IP network encryptor — what protects classified network traffic."

TACLANE is the box that sits inline on a network connection and encrypts the IP traffic — KG-175 family hardware, NSA-certified Type 1, the standard for protecting classified network traffic across the DoD. Every classified network at scale has TACLANEs at the boundaries. The devices require keys (loaded via Simple Key Loaders or modern equivalents) and have strict handling requirements as Controlled Cryptographic Items (CCI). Operators rarely touch them; the COMSEC custodian and the signal/cyber staff own the lifecycle. "The TACLANE is down" is a serious problem; "the TACLANE needs to be rekeyed" is a planned activity.

Narrowband ultra-high frequency satellite communications used by deployed forces for voice and low-rate data on the move, served primarily by the Ultra High Frequency Follow-On (UFO) legacy constellation and the Mobile User Objective System (MUOS).

"Narrowband UHF satellite communications for tactical voice and data."

TACSAT is what tactical forces actually use when they need to talk over the horizon — a UHF handset push-to-talk into a satellite constellation. The legacy UFO satellites and the MUOS constellation provide this service, with MUOS providing higher capacity and waveform sophistication. TACSAT channel allocation is famously oversubscribed in any major contingency; getting a guaranteed channel for a mission is a tasking-level fight that happens in CCMD J-6 channels.

The legacy term for the standardized digital data links used to exchange tactical information between command and control systems, sensors, and weapons platforms — now generally referred to by the specific link designations (Link 11, Link 16, Link 22, MIDS).

"The legacy term for tactical data links between military platforms."

TADIL is the legacy designation; current doctrine uses the specific link names. The point of any TDL is to move tactical data (track positions, targeting information, command messages) between platforms in a machine-readable format that integrates with onboard combat systems. Link 16 is the dominant joint TDL; Link 22 is the maritime successor to Link 11; MIDS is the radio that carries Link 16. Knowing which link your platform is on, and what it sees, is one of the basic forms of fluency for naval and air operators.

The general category of standardized digital communications links used to exchange tactical information (positions, tracks, targets, commands) among combat platforms, fire-control systems, and command-and-control centers — including Link 16, Link 11, Link 22, the common Variable Message Format (VMF) family, and other service-specific links.

"The umbrella term for tactical digital data links between platforms."

TDL is the umbrella term that covers all the digital data exchanges between tactical platforms — Link 16 (the joint workhorse, mostly UHF), Link 11 (legacy HF/UHF surface and air), Link 22 (Link 11 modernization, NATO-focused), and VMF (Variable Message Format, used on land combat systems). The historical term "TADIL" (Tactical Digital Information Link) is still occasionally used. TDLs are how an F/A-18, a Patriot battery, and an AEGIS cruiser share a common picture of what's in the air. TDL standards and implementations are highly disciplined — interoperability across services and allies is the point.

The US Space Development Agency's LEO proliferated constellation tier providing low-latency tactical data communications, including beyond-line-of-sight Link-16-compatible mesh networking and other tactical data relay services — Tranche 0 demonstration satellites launched 2023-2024, Tranche 1 operational satellites launching mid-to-late 2020s.

"The PWSA layer for tactical data relay — Link-16-from-orbit and beyond-LOS comms."

Transport Layer is the PWSA tier built around tactical data movement — Link 16-compatible mesh networking from orbit, beyond-line-of-sight tactical comms, and the data-relay backbone for the rest of the proliferated architecture. The technical concept: a LEO constellation that any tactical platform can talk to without needing a high-end terminal, with the constellation routing the data wherever it needs to go. The Tranche 0 demonstration satellites are validating the technical concept; Tranche 1 fields the first operationally meaningful capability. Transport Layer complements (rather than replaces) the existing AEHF, WGS, MUOS, and commercial-augmented SATCOM mix.

A proprietary Trellisware-developed software-defined mobile ad-hoc networking waveform used on multiple HMS-family radios (PRC-148, PRC-152, PRC-163, PRC-158 and others), supporting larger node counts and longer-range mesh performance than legacy SRW — the mesh waveform emphasized in modern Army Integrated Tactical Network capability sets.

"The current preferred mesh waveform — bigger nets, longer ranges than SRW."

TSM is what most ITN-fielded formations are actually meshing on — Trellisware's waveform scales to larger node counts and tolerates the realities of dispersed tactical formations better than the legacy SRW. The waveform runs on the PRC-163 Leader Radio (handheld) and the PRC-158 (manpack), forming a self-healing network that survives node loss and movement. TSM is one of the technical reasons ITN Capability Sets feel different than the WIN-T era — small radios doing big things without infrastructure. Operators rarely interact with the waveform directly; the radio handles it.

The radio frequency range 300 MHz - 3 GHz, the workhorse band for tactical SATCOM (MUOS, legacy UFO), line-of-sight tactical voice and data (HMS-family radios in their UHF modes), and aviation tactical communications (HAVEQUICK, Link 16) — the most heavily used band for modern tactical military communications.

"The 300 MHz - 3 GHz band — SATCOM, aviation, modern tactical radios all live here."

UHF is the band that does most of the modern tactical-comms work — UHF SATCOM (MUOS, legacy UFO), UHF line-of-sight from HMS radios, aviation HAVEQUICK frequency-hopping, Link 16 tactical data links. The propagation behavior is line-of-sight (with some terrain refraction): you can talk to what you can see, more or less. UHF SATCOM is the band most tactical radios use when they "go to satellite." Spectrum management (ATP 6-02.70) gets contentious in UHF because everything wants to live there.

The DoD-standardized bit-oriented variable-length message format used for tactical data exchange among ground combat platforms, dismounted systems (BFT, JBC-P), and supporting command-and-control systems — defined by MIL-STD-2045-47001 and related standards, the workhorse data format for land tactical mission systems.

"The land-tactical data format — what BFT and JBC-P actually exchange."

VMF is the message format that ground tactical systems use to talk to each other — Blue Force Tracker, JBC-P, the older FBCB2, fire-support systems, and many other land combat platforms exchange VMF messages over their data links. The format is bit-oriented and variable-length (hence the name): small messages are small, big messages are bigger, and the field definitions are tightly disciplined by MIL-STD-2045-47001. VMF doesn't look like much to an operator — it's the underlying protocol that makes "the blue icons updated on the map" actually work.

The current DoD wideband satellite communications constellation, providing high-throughput X-band and Ka-band communications for tactical and strategic users globally, replacing the legacy Defense Satellite Communications System (DSCS).

"The DoD current wideband satellite communications constellation."

WGS satellites began launching in 2007 and provide the high-throughput general-purpose layer of MILSATCOM — the layer that handles most of the imagery, video, and data DoD pushes through space. Several partner nations share access through cost-sharing arrangements (Australia, Canada, Denmark, Luxembourg, Netherlands, New Zealand). The constellation has grown over more than a decade of incremental launches as legacy DSCS satellites retired.

The US Army's tactical network program from 2003 to approximately 2018, providing high-capacity IP-based network services to brigade and below via satellite, line-of-sight, and beyond-line-of-sight links — terminated in 2018 after persistent affordability and capability concerns, with the Integrated Tactical Network (ITN) approach replacing the WIN-T model.

"The legacy tactical network program — terminated and replaced."

WIN-T was the Army's answer for "extend the enterprise network to the tactical edge" — large satellite trailers, complex terminals, expensive infrastructure that gave brigade-and-below formations IP connectivity. It worked in COIN-era stationary FOB environments. It did not survive the shift to large-scale combat operations thinking: the equipment was too heavy, too signature-prone, and too dependent on stationary footprints. The Army terminated the program in 2018 and pivoted to the Integrated Tactical Network (ITN) — smaller commercial-derivative equipment, mesh waveforms, incremental Capability Set fielding. If a leader mentions "WIN-T" approvingly, they're describing a previous era.