Interoperability Basics: How Agencies on Different Systems Actually Talk to Each Other

The core problem, in plain terms

Two neighboring departments can be a mile apart and still be unable to key up and talk to each other on scene. The reason is that radios only communicate when they agree on almost everything: the frequency band, the technology (analog versus digital), the system type (conventional versus trunked), and, on many systems, encryption and access codes. A crew whose radios are built for one system simply will not find the other agency's talkgroup, no matter how loud they shout into the microphone.

Why this happens is mostly history and geography. Departments bought equipment at different times, on different budgets, under different bands allocated to them, and often from whichever vendor won a contract that year. Each choice was reasonable on its own. Stacked across dozens of agencies in a region, the result is a patchwork where mutual-aid partners are technically incompatible right when they most need to cooperate.

The stakes show up at exactly the wrong moment. Interoperability problems rarely bite on a routine call inside one jurisdiction. They surface at the large, fast-moving, multi-agency incident: the wildland interface fire, the mass-casualty crash, the flood, the search that crosses three county lines. Those are the incidents where an incident commander needs to move resources and warn crews of hazards, and where a comms gap becomes a safety problem.

Shared common and mutual-aid channels

The oldest and most reliable answer is also the simplest: reserve a set of shared channels that every agency programs into every radio and agrees to use for cross-agency work. These are commonly called mutual-aid or interoperability channels. Because they live in the radio already, crews can switch to a known common channel and talk without any equipment bridging anything.

Standardized naming is a large part of what makes this work. National and regional plans define common channel sets and, just as importantly, standardized names so that a channel called by its agreed name means the same thing to a firefighter from any agency. When everyone's radio shows the same label, an incident commander can say the channel name over the air and expect every crew to find the same place. The exact channels, plans, and naming conventions that apply to you are regional, so confirm the current set with your regional or statewide communications authority rather than assuming.

• Pre-programming is mandatory. A common channel only helps if it is already loaded in the radio. Adding it during the incident is not an option.
• Discipline is mandatory. Shared channels are shared. If several incidents or agencies all use the same common channel at once, they step on each other. Plans usually spell out which channel is used for what, and dispatch or a communications leader assigns them.
• Coverage still matters. A common channel is only useful where radios can actually reach each other or a repeater. Terrain and distance do not care about the plan.

Gateways and patches that bridge systems

When two agencies genuinely cannot share a channel, a gateway (also called a patch or an interoperability bridge) can join them. In simple terms, a gateway is a device that takes audio from one radio system and re-transmits it onto another, so that a talker on System A is heard on System B and vice versa. It literally bridges two otherwise incompatible worlds by relaying the voice traffic between them.

Gateways come in fixed and portable forms. Some live permanently at a dispatch center or a regional hub. Others are deployable units brought to the incident and set up by trained personnel. Either way, the gateway ties specific channels together for the duration, then is taken down when the incident ends.

Gateways are powerful because they can connect nearly anything to nearly anything, including different bands and different technologies. That flexibility is also their weakness, which we cover in the tradeoffs section. A patch is a tool for when nothing simpler is available, not a first resort.

Shared regional and statewide systems

The most complete fix for interoperability is for agencies to operate on the same system in the first place. Shared regional and statewide radio systems are built exactly for this. When many departments are members of one large system, they can be assigned to talkgroups that let them communicate directly, without gateways or common-channel gymnastics, because they are already on common infrastructure.

Shared systems trade local independence for regional reach. A department that joins one gives up some control (it is now a tenant on someone else's system) in exchange for native interoperability with every other member, wider coverage from a larger network of sites, and shared maintenance costs. For many regions this is the strategic destination, reached over years of planning and funding.

• Membership is a governance decision, not just a purchase. Joining involves agreements about cost sharing, priority, talkgroup assignments, and who can talk to whom.
• Not everyone will be on it. Even a strong statewide system rarely covers every agency you will ever work with. You still need common channels and gateways for the partners who are not members, including out-of-area resources that respond to big events.

Swapping radios and console patches

Two lower-tech methods round out the toolkit, and both are worth knowing because they are cheap and they work.

Swapping or caching radios means handing an incoming agency a radio that already works on your system. Many regions maintain caches of programmed portable radios that can be issued to mutual-aid crews or to a liaison from the responding agency. The visiting company then carries a radio that speaks the host system natively. It is blunt but effective, and it sidesteps every compatibility problem at once. The costs are logistics (someone has to store, charge, program, issue, track, and recover the radios) and the learning curve of handing a firefighter an unfamiliar radio mid-incident.

Console patches at dispatch are a form of gateway performed at the dispatch center. A telecommunicator can electronically tie two or more channels or talkgroups together at the console, so traffic on one is rebroadcast on the others. This is fast to set up for a dispatcher who is trained on it and needs no field equipment. It shares the same downsides as any patch: it consumes channel capacity, it can add a small delay, and it depends on the dispatcher managing it correctly and remembering to take it down.

The tradeoffs of each approach

No single method is best. Mature regions keep several available and choose based on the incident. The honest tradeoffs:

• Common channels: simple, robust, and need no special equipment, but require every radio to be pre-programmed correctly and every user to follow channel discipline. They also depend on coverage in the area of the incident.
• Gateways and patches: connect almost anything, but a patch can introduce a slight delay, and it ties up a channel on every system it joins for as long as it is active. Overuse a patch and you can congest multiple systems at once. Patched audio can also confuse users who do not realize two groups are joined.
• Shared systems: the cleanest technical answer, but the slowest and most expensive to reach, and never universal. You still need fallbacks for non-members.
• Radio swaps and caches: defeat every compatibility issue, but add real logistics and hand people unfamiliar equipment.
• Console patches: fast and equipment-free for the incident, but carry the same channel-loading and delay costs as any patch and lean entirely on a trained dispatcher.

The human side: governance, SOPs, and training

Here is the point that experienced communications leaders return to again and again: interoperability is not a box you buy. It is people, process, and technology together. This is the well-established principle behind the SAFECOM interoperability continuum, which frames interoperability across several dimensions (governance, standard operating procedures, technology, training and exercises, and usage) rather than treating it as an equipment problem alone. The fanciest gateway in the region fails if nobody is trained to deploy it, if there is no agreement about who controls it, or if crews have never used it before the day it matters.

Governance and agreements come first. Before any incident, partner agencies need shared decisions: who can request mutual-aid comms, which channels and talkgroups are assigned to which purpose, who has authority to establish and take down a patch, and how out-of-area resources are brought in. These live in written mutual-aid agreements and communications plans, not in someone's memory.

Standard operating procedures turn agreements into action. An SOP says, in plain steps, how to switch to the common channel, how to request a patch, how the dispatcher documents it, and how command organizes talk paths at a growing incident. Standardized channel names feed directly into these SOPs so the words spoken over the air are unambiguous.

Training and exercises are what make it real. Regular drills that force agencies to actually connect (switch to the common channel, stand up a gateway, issue cache radios, patch at the console) are the only way to find the gaps while they are cheap to fix. The programming error, the coverage hole, the dispatcher who was never shown the patch procedure: you want to discover these in a Tuesday exercise, not at 3 a.m. on a mutual-aid structure fire.

Takeaways

• The core problem is incompatibility: neighboring agencies often run different bands, technologies, and systems that cannot natively hear each other, and it bites hardest at large multi-agency incidents.
• There is a toolkit, not a single fix: pre-programmed common and mutual-aid channels, gateways and patches, shared regional or statewide systems, radio caches and swaps, and console patches at dispatch.
• Every method has tradeoffs. Common channels need pre-programming and discipline; a patch adds delay and ties up a channel on every connected system; shared systems are the cleanest answer but slow and never universal.
• Standardized channel names and shared programming templates prevent the classic failure of a mutual-aid channel that is missing or mislabeled in half the fleet.
• Interoperability is governance, SOPs, training, and usage as much as equipment. The SAFECOM continuum captures this: people plus process plus technology, not just a device.
• Exercise it before the incident. The fanciest gateway fails if nobody trained on it, and the gaps you find in a drill are cheap; the ones you find on scene are not.
• Regional plans vary. Confirm the specific channels, names, and procedures that apply to you with your regional or statewide communications authority.