GenWatch3®  Commander Host Bundle

(Replacement for SIMSII Server)

At the right you see the architecture diagram for GenWatch3®  Commander Host. Let's take a tour.

CORE: The blue/green box (inner) in the middle contains all of the GW3 CORE elements. These are the minimum elements that must be purchased to make GW3 run. One exception to that is the green Halcyon module. This will be explained later.

Application Interfaces: The violet box (outer) contains the optional interfaces for GW3. As we said, what you see to the right are all of the modules that we are bundling for the SIMSII replacement. This bundle is almost every option that we offer for GenWatch3® . There are a few not in that box since they fell out of the 'equivalent facility' replacement criteria, but they can be purchased separately from Genesis. 

External Devices (clockwise)

RF-modem/RIMII: As you will see in other sections, these are supplied by the customer. Quite possibly these are in place already. Please be aware that the RF-modems need to be capable of and programmed with the correct firmware to be rebanded. The RIMII must be a RIMII and not RIMI. You will notice that there are two sets. One is used for receiving the control channel data (the OSWs) and one is used to transmit commands to the control channel (ISWs). We call this full duplex operation. If, for some reason, one of the RF-modem/RIMII sets fails, GenWatch3®  will AUTOMATICALLY reconfigure itself to operate in simplex mode where the remaining RF-modem/RIMII is normally in receive mode and only switches to transmit mode when necessary. The user will receive notification of the problem. Click here to see more.

External USB Electrical Relay Box: This comes with the bundle. It is the Ontrak AU208. With this box, you can have GenWatch3 Commander close a relay that sets off lights and bells if an emergency is not acknowledged within a set period of time (as an example). You can see the specifications from the manufacturer's web site by clicking here.

Central Controller: We are supporting customer supplied 6809 controllers and the MTC3600 with the rebanding firmware in place. We do support main and backup controllers. We are certifying our solution for CIT interconnect for all features, and only the MSAVE/MLOAD for the MBX interconnect at this time.

Dial In Support: This can be a standard POTs (plain old telephone) phone line or a broadband connection. It does not need to be full time. You can connect it as needed for support. Since we will ship with pcAnywhere and it will be only used for remote Genesis support, it is possible for the customer system administrators to also use this connection to remotely access GenWatch3®  to manage their system. If your IT department is fairly proficient, you can easily use a VPN connection and pcAnywhere to remotely access also. Broadband is always better!

16 Port Serial Port Block: This is also called the RocketPort connection 'brick'. This is used for the connection point for any CAD systems (up to 4) and any direct RS-232 connections to central controllers. The block ports will be labeld for easy identification of where to connect devices. You can see more about the 'brick' from the manufacturer's web site by clicking here.

CAD Connections: There are a number of Computer Aided Dispatch software companies. Some have made interfaces to connect their software to this CADI (computer aided dispatch interface) API (application programming interface). This API information is included on the GenWatch3®  Commander CD for CAD companies to verify their connections or to create connections to the SmartNet system commands via GenWatch3®  Commander. Click here to see more.

Customer Ethernet LAN: This is what it sounds like. The customer's existing LAN. GW3 Commander Host does NOT have to be connected to the customer's LAN if there are no GW3 Commander Clients connected. If there are no Clients, it is permitted to have the Host on the client LAN.

GenWatch3®  Client Computers: The certified Client will be the the one that is the GW3 Client Bundle. The Client CPU is almost identical to the Host CPU. The major difference is that there is far less software licensed for the Client. Look below in the Client Bundle section for more detail.

 

 

RF-modem & RIMII

 

 

Ontrak ADU208 External Relay Box

 

Motorola 6809 & MTC3600 Central Controllers

 

 

 

16 port serial interface 'brick'

CORE Elements (clockwise)

 

GenWatch3®  Service: The red box in the center is GenWatch3®  Service. If you come from a DOS world, you might know this as a TSR (Terminate Stay Resident) program. Windows runs many many services on the average machine to do tasks behind the scenes. The GW3 Service 'brokers' everything that happens in GW3.  There is not a direct interface for the GW3 Service but the other GUI interfaces tell the GW3 Service how to act and react.

RIMII Communications Module: This module does all of the major control channel decoding and encoding (OSWs and ISWs). In the GW3 Commander Host configuration, this is the only place you will find this module. The GW3 Commander Host is licensed and certified to handle only one set of RF-modem and RIMIIs. By design, it can accommodate up to five sets. Contact Genesis after your Motorola warranty period for more information.  Click here to see more.

Trigger Module: In the CORE area, this is the module that handles all of the decisions that are set up from the Trigger interface. The Trigger interface is discussed in the next section. 

Security Module: This is where all security decisions are made. Among other things, it determines, based on the security setup, if a user is permitted to have access to various parts of GenWatch3®  Commander.

SysLog Module: This is a powerful module to log every significant event inside GenWatch3® . This is very helpful for diagnostic purposes. The results of the SysLog can actually be located anywhere from right on the GW3 Commander PC to remotely at Genesis (with appropriate network connection).

GenLicense Module: This has no interface. Behind the scenes, this module assures that your GW3 Commander is only permitted to operate on system(s) and have modules that are licensed to it. Our licensing procedure, while it may seem complicated by some, mimics the way Microsoft licenses its products. We use 'soft' keys that are highly encrypted with 3D hash, 128bit encryption.

Halcyon: It is a word that means peaceful, tranquility. It is the opposite of "tempest". The goal of this module it to handle all RCM (Radio Command Management) requests whether they are from the GW3 Commander interface or if they are from the CADI interface, and broker them to the control channel in an orderly fashion.

Group Module: Based on the setup you have done, this module gathers all of the usage information for Talkgroups that you want to watch and prepares that information for display by the Group Interface.

Activity Module: All control channel activity passes to this module. Based on the setup you have done for fonts, colors, filters, etc., the data is passed on to the Activity Interface for viewing.

Alias Module: As it sounds, this handles all alias information stored in GW3 Commander. This not only handles the proper brokering of the radio alias information for all modules, it also handles the aliases you define for Talkgroups, systems, channels, sites, statuses, messages, etc.

Archiver Module: This module does a lot of 'heavy lifting'! If you want to store all of the control channel data, this module makes that happen. As you will see in the Archiver Interface description, you can setup the detail level of what you want to archive, how long you want it archived and where the archive database file is located (by default in GenWatch3®  Commander, it is located on the GW3 Commander Host but it is possible under Genesis supervision to move it to another location).

System Summary Module: This drives the System Summary Interface. As you will see in its description, there are many numbers from the live system activity that are summarized and displayed in one place. They can be graphed on the screen and updated dynamically every 5-60 seconds. This module handles all of the 'back office' tasks to make the display operate. 

Interface Elements (clockwise)

RIMII Communications Interface: This interface allows you to enter information about your system such as the ID, control channel frequencies, and much more.

Trigger Interface:  This is where you can set up what to do when certain events happen. Some events that you can trigger on are: Emergency, unattended receipt of an Emergency alarm (no users logged in), DIAGs, a Status, a Message, a PTT from a specific ID, a lack of PTT from a specific ID within a period of time, and more. You can then select how to be alerted.  You can elect to alert the PC with audio and visual alarms (you select the WAV file to play), or if you want to close a relay  on the ADU208, you can then set off bells, sirens, lights, open doors, etc. Click here to see more.

Security Interface: This is where all security roles are created, users of GW3 Commander are entered, and what they can and cannot do is assigned here also.  Click here to see more.

SysLog Interface: This is a powerful module to log every significant event inside GenWatch3® .

LaunchPad Interface: You'll get to know this one very well as all GW3 Commander things start here.

EzSaveWin: This replaces Advanced SMT.  Click here to see more.

RCM Interface: This is the location from which all RCM commands are managed. Click here to see more.

Halcyon Interface: It is a word that means peaceful, tranquility. It is the opposite of "tempest". This interface allows you to control the function of the Halcyon module.

pcAnywhere: This is a separate program from Symantec that comes loaded on your GW3 Commander machine. We put this on all machines. The primary use is for Genesis to provide remote support. A secondary reason is to allow remote operation of EzSaveWin from any GW3 Commander Client machine. We have strong reasons for operating EzSaveWin this way.

Group Interface: Based on the setup you have done, this module gathers all of the usage information for Talkgroups that you want to watch and prepares that information for display by the Group Interface. Click here to see more.

Activity Interface: All control channel activity can be displayed in this interface. Or, very little information can be displayed. This interface allows you to control the filtering of the data (what you see and don't see in the interface), the colors assigned to each data type, the font, and if you right click on any data element in the screen, you can see an incredible amount of additional information about that data. Click here to see more.

Alias Interface: As it sounds, this handles all alias setup input stored in GW3 Commander. Click here to see more.

Archiver Interface: You can setup the detail level of what you want to archive, how long you want it archived and where the archive database file is located (by default in GenWatch3®  Commander, it is located on the GW3 Commander Host but it is possible under Genesis supervision to move it to another location).  Click here to see more.

System Summary Interface: There are many numbers from the live system activity that are summarized and displayed in one place. They can be graphed on the screen and updated dynamically every 5-60 seconds. This module handles all of the 'back office' tasks to make the display operate. Click here to see more.

GenWatch3®  Commander Client Bundle

(Replacement for SIMSII Terminals)

If you click the image at the right, you can see what is included on the Commander Client machine. It should be obvious, but a Client machine cannot operate without a Host machine being present on the LAN. You'll notice the absence of the CORE modules that are present in the Host bundle. In fact, it may not look like much going on in the Client compared to the Host. All of the interfaces are present and they 'look' back to the Host for their information.

LaunchPad Interface: You'll get to know this one very well as all GW3 Commander things start here.

Activity Interface: All control channel activity can be displayed in this interface. Or, very little information can be displayed. This interface allows you to control the filtering of the data (what you see and don't see in the interface), the colors assigned to each data type, the font, and if you right click on any data element in the screen, you can see an incredible amount of additional information about that data.

RCM Interface: This is the location from which all RCM commands are managed.

pcAnywhere: This is a separate program from Symantec that comes loaded on your GW3 Commander machine. We put this on all machines. The primary use is for Genesis to provide remote support. A secondary reason is to allow remote operation of EzSaveWin from any GW3 Commander Client machine. We have strong reasons for operating EzSaveWin this way.

Group Interface: Based on the setup you have done, this module gathers all of the usage information for Talkgroups that you want to watch and prepares that information for display by the Group Interface.

GenWatch3 Reports: Reports can be run from the Host or the Client. Your results will always be faster if they are run from the Client. The GW3 Commander Client comes with all of the reports on each machine. All reports 'look' back to the Host where the Archive Database is located.

Alias Interface: As it sounds, this handles all alias setup input stored in GW3 Commander.

System Summary Interface: There are many numbers from the live system activity that are summarized and displayed in one place. They can be graphed on the screen and updated dynamically every 5-60 seconds. This module handles all of the 'back office' tasks to make the display operate.