There is Nothing Cookie Cutter About Genesis GADI

It’s no secret that technology moves quickly.  To the dismay of some, it often moves much quicker than they are comfortable with as it presents new learning curves and/or processes.  Unfortunately for those resistant to change, this trend is likely not to go away any time soon.  But…there is a bright side.  In some circumstances, opportunities open up that can help bridge the old to the new, making the technological journey easier to bear.  One such example manifested when Motorola introduced their MCC7x00 Series Dispatch Consoles.

Dispatchers are known to be quite particular in how they manage their daily tasks, which is completely understandable given how much multitasking they are required to do.  So when their legacy dispatch consoles were replaced with the MCC 7×00 consoles, they recognized how much they missed some of the workflows they became accustomed to, such as being able to use a keyboard to execute their tasks vs. a mouse.  And with that, in March 2010, Genesis’ GADI was born.

GADI screen with MCC 7500 consoleGADI stands for Genesis Aided Dispatch Interface.  The software’s prime objective is to enhance the standard features of the MCC consoles.  Since its inception, GADI’s functionality has grown significantly and continues to do so based on regular customer feedback.  As a matter of fact, the ongoing development, much of which is custom, is one of the main benefits of GADI.  No one GADI solution is the same because the needs of all Dispatch Centers are not the same.  The more acquainted with the software dispatchers become the more unique requirements that bubble to the surface.  There are instances where the custom elements have utility outside of those that made the request, which is why all GADI licenses are sold “a la carte”.  There is no base package so the customer only pays for features they use which strengthens their return on investment.

In addition to the custom design, another reason dispatcher’s value GADI is its customizable interface.  Each individual tab is able to be moved around, minimized, or displayed on another screen.  The GADI Interface can even be locked in place in order to keep important information front and center at all times.

Now, you’re probably curious about the type of functions that exist with GADI.  At a high level, GADI provides its users with a means to improve resource management, streamline workflows, and enhance dispatcher satisfaction.  Following is a list of the software’s more popular features that truly embody these value statements:

  • Centralized Patch allows dispatchers to share patch access among all permitted consoles. Important patches can also be made permanent.
  • With Active Patch, dispatchers can easily find the resources that are in use and on what console position. This is especially helpful when starting a new shift.
  • Unattended Emergency was designed for non-critical agencies (think Municipal Utilities) or secure radio users (think Tactical Teams) that prefer to not have their talkgroups monitored unless they are in an emergency situation.
  • Configurable Input Devices (CID) are “keyboard-like” accessories that attach to the MCC console and perform various action scripts with the single press of a button. You could say they are the epitome of all things GADI.  The layout is completely customizable, fewer steps are required to carry out a task which saves the dispatcher time, and both of these combined improve overall satisfaction.

As I alluded to earlier, the essence of GADI is that its development is 100% customer-driven.  Here are some recent or notable use cases, which are now part of the GADI suite…

  • Dispatchers want the ability to control, on a resource by resource basis, where emergency alarms are played. With Emergency Volume & Tone Management, dispatchers can select which individual resource they want to be played in their selected speaker.
  • For those that use an Instant Recall Recorder (IRR) to start and stop the replay of audio, GADI can integrate with the IRR’s API and avoid having to toggle between the IRR and GADI interface. Some have taken things further and added an IRR toggle button to their CID.
  • Should a system enter into trunking of failsoft mode, the Trigger function could be used to send distinct audible or visual notifications to the dispatcher. Similarly, another notification could then be sent when the system has returned to wide-area trunking.

Because GADI is not a one size fits all solution, the system design really should stem from a more consultative approach.  Your Genesis Sales Expert can help coordinate a meeting to discuss the requirements and expectations of your dispatch environment.  To better prepare for that discussion, we have quite a few resources to get you even more acquainted with GADI, including a GADI Solution Brief and a two-part 30 Minute Thursday webinar series which sort of demos some of the features discussed here, and more.  Watch the demo to see what I mean 🙂.

Until next time…little by little, day by day, what’s meant for you will find its way!