Our comparisons were compiled from various Motorola published documents and Genesis published information. In the available Motorola documents from 1996 to present, some features have been renamed over time. We have made our best effort to consolidate these various names. We have aimed our modules at the current Site Lens while having an eye toward including SIMSII and SIP features. The reason is that Site Lens was created by Motorola as a Windows based alternative for SIMSII. Please contact Phil Burks, Michael Rainer, or Kelley Clarida for timing of new developments.

GenWatch3™ (GW3) in its basic model form is a stand alone Windows based software alternative for monitoring a Motorola SmartNet system or a single site on a SmartZone system. With licensing from Motorola, we have created the GenWatch3™ Commander Series in an effort to provide a direct replacement for SIMSII and SIP. It is also an alternative for System Watch and Site Lens products since we have covered additional features that were unique to those network management products. All features and functionality of all named Motorola products are being rolled into GW3 Commander. GW3 is very modular and every attempt has been made to make the construction of the module building blocks to be able to replicate the construction of Site Lens. However, there are differences (mainly in the CADI port). Those differences will be pointed out in our documents.

The GW3 Commander bundles come licensed for operating on one SmartNetII+ system at a time. That can grow. In some restricted conditions, GW3 (non-Commander, without RCM) can even be operated very nicely on a SmartZone system. If the SmartZone system is totally simulcast or if there are fewer than 5 sites are just two examples. If you only wish to monitor some sites on a wide area SmartZone system, this is also another case for using GW3. Please contact Genesis System Engineering for specifics.

While the GW3 Commander Series Bundles make life and ordering very simple through the Rebanding and Motorola sales process, our fundamental GW3 design took the approach that one size does not fit all. Almost every sub system in GW3 is modularized to give it ultimate flexibility. Modules do not necessarily need to reside on the same PC if there is adequate LAN bandwidth between the modules. The largest consumer of CPU resources is the GW3-ARCHiver. If this option is not purchased, a large number of systems and/or modules can be operated from one single machine. Likewise, if the GW3-ARCHiver is relegated to its own server, many other modules can cohabitate on a single PC. All of this flexibility does add to complexity. Contact Genesis for more complete answers to your questions.