Here we've provided an overview of the differences in the most popular interoperability technologies being deployed.  See below for analysis of these capabilities.

Analysis:

Project 25

Project 25 radios and infrastructures don't necessarily include IP interfaces and Radio over IP functionality.  Most IP functionality is additional infrastructure and/or interfaces.  Primarily, Project 25 provides compatibility of radios operating in digital mode with other P25 radios operating in the same band and on a P25 infrastructure.  Optional and additional IP interfaces provide the mechanisms for interoperability with non-P25 equipment and equipment in various bands (UHF, VHF, 800, etc).

ACU

The ACU-1000, ACU-T and TRP-1000 provide low cost ways to cross-patch multiple systems.  They are powerful systems with many control parameters that enable reliable and high quality links.  The set-up is the key.  It's important not to expect a "plug and play" implementation. 

With the recent addition of WAIS (Wide Area Interoperability Software), multiple ACU's can now be connected to cross patch systems across an IP network without geographic limitations.  The user interface is well done and easy to use.

The unit will not enable you to remotely change talk groups or channels on the radios connected to the ACU.  This can be an issue because the channels or talk groups that you monitor and/or cross patch for day to day operations may be completely different than for events and incidents.  Users generally prefer cross patching to occur at the command level and want to avoid linking all users together. Extra radios set on interoperability channels and additional interface modules can overcome this limitation.

Links can also be set-up and torn down via the DTMF keypad on mobiles and portables, but it is not as elegant as other solutions.  Users would have to memorize command codes and systems to make this work.

The requirement of an NXU (hardware interface) for each "Radio over PC" user should not be a problem when the number of users is small.

Catalyst

The most often over-looked requirement of interoperability involves channel monitoring.  Long before members of different organizations want to speak to each other they simply want to know what the other agencies are doing.  They need to monitor each other's incident, operational and tactical channels without keying-up each other's system. 

Why is this significant?  Because agencies usually don't want you to "patch" to these working channels.  If you have to patch, then they'll provide a separate interoperability channel.  This means the dispatcher will have to change channels, which is so cumbersome on other devices that it can be impractical.  On the ACU for instance, you'll have to make changes on the control heads of the radios that are directly connected to the ACU, and these control heads are not within arms reach of the dispatcher.   

Conversely, Catalyst enables you to have complete control of the radios, including channel changing, from the dispatcher's software interface.  It's the only solution that makes it this simple on the dispatcher no matter which radio manufacturers are being used.  Furthermore, instead of relying on 8-12 radios connected to an inter-connect device, you can simply use 2 or 3 with up to 99 channels programmed into each.

The catalyst solutions are also ideal for remote dispatch capabilities and remote radio control.  It shines in situations where you want the ability to change talk-groups/channels, make Individual Calls, use Caller-ID, declare emergencies, etc.   The "Radio over PC" via software is also more convenient than additional hardware interfaces.

NetworkFirst

M/A-Com's NetworkFirst solution is an IP based, network-centric approach to interoperability.  It's powerful and elegant, and that's reflected in the price.  M/A-Com has scaled the system to offer an alternative to the ACU while offering customers the growth potential to more elegant strategic system deployments.

It shares similarities with the ACU and Catalyst in that it leverages IP Networks, but takes it a few steps further.  One notable difference is the elegance by which the portable/mobile user can set-up and take down cross-patches.  They employ the concept of "talk-groups", whereby predefined cross-patches are programmed into radios and selectable via a control knob.  Not only is it easier than using DTMF codes, but alpha-numeric displays will tell users exactly what they're doing.  Users will like this level of control because it's quick, easy and doesn't require anything from dispatch.  This radio functionality works with trunking systems and with conventional systems using P/L tones.

Most unique is how the NetworkFirst solution is built upon the VIDA Platform, sharing switching equipment, management and administration systems with M/A-COM's P25 voice, data and broadband public safety solutions.  Doing so makes the IT support of these networks easier, more efficient and less costly.

The following is a comparison document that shows the differences in the NetworkFirst technology and why it's a more robust, strategic interoperability solution than other IP-based solutions.  <NetworkFirst Comparison>

RACOM Network

The RACOM Network is an existing 800 MHz trunked radio network that covers multiple states.  It's ideal for state resources that may be deployed anywhere throughout the state and still need radio coverage.  Likewise, local and regional agencies and services may find it very expensive to build-out their own coverage area across large geographies.  Purchasing just the radios and using this existing network may be the most robust and economical solution.  It also inherently provides the opportunity for interoperability between the different users on the system - without any additional cost.

The Network is currently used by a host of public safety, utility and other mission-critical users.  See customer sampling.