Genesis–Making Motorola Trunking Systems Better Since 1983
Time at Genesis:
GW3 Commander Series HomeGenWatch3® Commander HOME
Use this link to go to the Commander Home Page. Read about it here.
GenWatch3 featuresGenWatch3 Features
GW3 listens, decodes, stores, reports, stores, watches, alarms and more! Read about it here.
GW3 Reporter PackageGenWatch3 Reports
GenWatch3 lets you view data in easy to understand and flexible reports.
how it worksHow It Works
Learn how this powerful, feature-packed, yet user-friendly program works here.
resourcesDownloadable Resources
Download PDF and PowerPoint files about GenWatch3 here.


Get notified by email when this page changes.


Privacy
ChangeDetection.com
» Home Page  |  » Products  |   » GenWatch3  |  » RCM

Radio Command Manager

Genesis has crafted our RCM module to be identical to the Site Lens RCM tool. You will notice the obvious look that is very similar to the Site Lens RCM and after using it, you will notice that the workflow is also similar. There is a method to all of that. After many hours of engineering discussions, Genesis and Motorola elected to not ask you to drastically change the way you have been doing your operations in this critical module. Of course, if you are coming from SIMSII, there is by its nature a giant step coming to Windows based technology. As is the nature of the Genesis approach to business, we will listen to our customers. If, over time, we learn from our field consultants (our customers) that there are improvements that we can make to make your life easier, we will add those improvements into RCM. GenWatch3 and the RCM DOES have a future with Genesis!

RCM is launched, like all other GW3 modules, from the GW3 LaunchPad. Below, you can see the main RCM screen. We call this the RCM Monitor window. If you click on the image below, you can see a much larger image. GenWatch3 Commander Host, and Client are bundled with all of the possible RCM commands. The GW3 Commander LE (the SIP replacement) only has a limited set of the RCM modules so you will not see all of the sub-windows that you see here.

Monitor system radio events, including:

  • Emergency Alarms
  • Change Me Requests
  • Statuses
  • Messages

Issue radio commands, including:

  • Call Alert
  • Request Radio Affiliation
  • Selective Inhibit / Cancel Selective Inhibit
  • Selector Lock / Selector Unlock
  • Dynamic Regroup / Cancel Dynamic Regroup
  • Dynamic Failsoft Assignment / Cancel Dynamic Failsoft Assignment
  • Storm Plans
  • Remote Monitor / Radio Trace

Also included is Database Snapshot. All of these have more detail below.


RCM Monitor Window




Selected RCM highlights

ID Selection: There are many radio commands that you will send that require a radio ID. GW3 RCM gives you a Radio ID Selector screen that makes this task much easier and it eliminates data entry mistakes. Click on the image to the right to see all of the possible ways you can search for a radio in GW3 Commander.


Issuing a Batch Command: There may be occasions that you want to send a Call Alert, Selective Inhibit, etc. to several radios at one time. GW3 RCM makes it easy to build a batch for this to happen with little involvement from the user. Notice that for tracking purposes, it is an easy thing to add a comment note about why you are sending this command.

Single Commands:

There are a few commands that only make sense to act on one radio at a time. Radio Monitor / Radio Trace (RMRT) is one of those commands. RMRT is extremely useful in a time when a person is in danger and cannot reach their radio. This could be a hostage situation, the person is down and unconscious, etc. The RMRT has the ability to open the microphone of the radio to allow authorized system operators to listen to the audio that is near that radio. The trace feature helps the system operator to find a radio by telling the radio to key up, with a tone, for 15-60 seconds. The system operator would then use direction finding equipment to locate the radio.

Database Snapshot is what it sounds like. It is a very quick 'report' of the last known status of a selected radio. Click on the image to the right and you will see all of the information that is quickly gathered and presented to the user.


Storm Plan: If you have used SIMSII or Site Lens for any period of time, you know that a Storm Plan is a predefined set of Dynamic Regroupings for a special event, like a storm or a parade. Storm Plans are defined in the GW3 Alias Manager interface. You create a name for your Storm Plan, add a description, define the type of command(s) that you'll be sending in the Storm Plan, add any more comments or descriptions, and save the plan.

Command Monitor Pane: This is the very top pane in the RCM Monitor window. There is a lot of information available in this pane. By the way, each of the panes in the RCM Monitor can be resized to help you see whatever you are working with at the moment. The elements that you can see in this pane are:

  • Status:  The collective status of the tasks within the command.
  • Command:  The basic command type.  These types include:
    • Radio Check
    • Selective Inhibit
    • Cancel Selective Inhibit
    • Regroup
    • Cancel Regroup
    • Failsoft Assign
    • Cancel Failsoft Assign
    • Selector Lock
    • Selector Unlock
    • Storm Plan:  Can contain the following task types:
      • Regroup
      • Cancel Regroup
      • Failsoft Assign
      • Cancel Failsoft Assign
      • Selector Lock
      • Selector Unlock
    • Call Alert
    •  RMRT:  Can contain the following task types:
      • RMRT Frequency
      • RMRT Talkgroup
      • RMRT Parameters
  • Target TG: Talkgroup targeted by the command (if any) if there is exactly 1 talkgroup targeted by all tasks.
  • Failsoft: Failsoft channel targeted by the command (if any) if there is exactly 1 failsoft channel targeted by all tasks.
  • Radio ID: Radio ID targeted by the command if there is exactly 1 radio ID targeted by all tasks.
  • Radio Alias: Radio Alias targeted by the command if there is exactly 1 radio ID targeted by all tasks.
  • Start Time: The date and time the command was issued.
  • End Time: The date and time the last task in the command completed (either successful or unsuccessful)
  • Dispatcher:  The dispatcher that issued this command
  • Comments:  Comment assigned to the command when the command was created
  • Reason:  The reason a task in the command failed, shown for the most recently failed task within the command (if any)
 
  Privacy Policy  |  Terms of Use  |  Notices  |  CHIFF  |  Products  |  Solutions  |  About Us  |  Contact Us  |  Site Map
All Rights Reserved © 1997-2008 The Genesis Group
a Burks GenCore Co., Inc. company.