Genesis–Making Motorola Trunking Systems Better Since 1983GenWatch3 home
Time at Genesis:
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  |  » Hardware Configurations

hardware configurations

Once a data packet is decoded, it is stored in one of several data tables, depending on the packet and depending on how you have setup GenWatch3®. GW3 allows you to store everything, nothing and all variations in between. This includes RAW Control Channel data!

How much hard drive space you will need is related to several things:

  • Your Daily Call Volume
  • How long you want to keep the history in each type of table in the database.
  • Do you want to store the RAW control channel data? Store it for how long?

In general, the larger the drive, the better. At the price of hard drives these days, it is very inexpensive (less than $150) to get even a 120GB HD and have more room than you want, plus 'wiggle' room.

GW3 can store your data for about a year. After one year, we highly recommend you migrate your database to another drive. We provide a simple interface to help you manage the length of time that you keep your data. In fact, you can keep some information longer than other information, it is your choice. Since all of the data is kept in SQL2005/07 files, you are really only limited by drive space. We recommend a 80GHD only because that should store control channel data from an average system for one year without having the RAW capture on. If you want to store it longer and/or if you want to capture 100% of your RAW control channel data for one year, you use a larger storage device. Remember that at today's prices, Hard drives are MUCH cheaper than gas for your car!

Disk Space Decision Factors
There is one basic thing that will greatly influence the amount of disk space that you will consume on a daily basis. Whether or not you store the RAW Control Channel data. Here are some decision factors to help...

There are about 20 tables in the GW3 database. If you set all of those databases to hold 365 days of data, and have the RAW data capture turned on, and your system averages about 25,000 calls per day (that's a fairly average system), it will consume about 175 MB/day, or 64 GB/year. Now, with the RAW data capture turned off, you will consume only 6.4 MB/day, or 2.5 GB/year. BIG difference! You have the option to turn the RAW data capture on and off whenever you want to. You can also set the RAW database to only keep the last 30 days, or only the last week. You get the idea.

So, when we say that a 80 GB HD will be fine for GenWatch3, you see how we arrive at that number. If you want to do your own approximate calculations, here are the numbers to use:

RAW DATA = apx. 169 MB / day
ALL OTHER DATA = apx. 6.5 MB / day

One additional thing to think about when you are sizing your Hard Drive for GenWatch3. Remember to leave additional room for the following things:

  • Operating System (see table)
  • MS SQL2005
  • MS Office (Excel)
  • Additional space for SQL maintenance needs (generally 3 times the raw storage space)

Summary of Hard Drive Sizing Factors:

  • Calls per Day (Call Volume)
  • Capture RAW data as well as processed data?
  • How long are you storing the RAW Data?
  • How long are you storing the processed data?

Hard Disk Speed
The quick answer is: the faster the better. GW3 (and our other products) do a lot of disk access for storing data and in many cases, simultaneously extracting data for reports. We have found that a 10,000 RPM drive will far outperform a 7200 RPM drive. Likewise, a 15,000 RPM drive, even though it costs more, will perform even faster reporting and other activities. If it is within your budget, we highly suggest going with 15k RPM drives.

Minimum Hardware Specifications by Purpose

  For 60 Day Demo Archiving for 1 year

With RAW Control Channel, Low redundancy
Archiving for 1 year

With RAW Control Channel,  High redundancy
Archiving for 1 year

With RAW Control Channel,  High redundancy, MAXIMUM Reporting
No Archiving, No Reporting (like GroupView)
CPU P4 P4 P4

Server:P4
Client: P4

P4
Operating System XP Pro Windows Server 2003 * Windows Server 2003

Server: Windows Server 2003

Client: XP Pro

XP Pro
Database SQLExpress MS SQL MS SQL

Server: MS SQL
Client: None

SQLExpress
MS Excel 2000 - 2003
X 
(if testing the reporting features)
X
X
X
(Client)
Security Software (NAV, etc.)
X
X
X
X
X
           
RAM 2 GB * 2 GB 2 GB Server: 2 GB
Client: 2 GB
2 GB
Available Hard Drive 80 GB 80 GB 120 GB RAID Server: 120G RAID
Client: 30 GB
80 GB
Suggested Monitor Resolution 1280x1024 1280x1024 1280x1024 1280x1024 1280x1024
CD or DVD
X
X
X
X
X
NIC Card
X
X
X
X
X
Keyboard / Mouse
X
X
X
X
X
Speakers
X
X
X
X
X
Modem
X
X
X
X
X
Internet Access for Support
X
X
X
X
X
pcAnywhere
X
X
X
X
X

Database Engine Limitations

  • SQLExpress
    The size of the database is limited to 4 Gigabytes and 1 PC (about 6 to 8 months conservatively of data depending on system use). Maximum of 8 concurrent connections. This is FREE. Does not require server operating system. Can run on a desktop PC.
  • SQL Server Workgroup Edition
    The size of the database is limited to 2 Gigabytes system memory, and has unlimited database size. It comes with a 5 user CAL that can be upgraded 5 CALs at a time. This has the price of SQL Server; however, a server operating system is not required, thus avoiding additional expense. Can run on a desktop PC.
  • SQL Server
    The size of the database is limited to size of hard drive. No maximum to the number of concurrent connections. The price is that of the SQL Server. A server operating system is required. May require a server class machine.

While running, GenWatch3 will use 2 of the concurrent connections for archiving and aliasing. GenWatch3 will also use other connections but frees them after each use. Therefore, if a customer has SQLServer in Personal Mode then there is a high probability of "throttling" if the customer does reporting.

The best scenario for a customer that does a lot of reporting is to have a separate Server Class Machine with a Server based operating system running SQL Server. On the other hand, if a customer only wants to watch the group screen with little or no reporting then MS SQL Express on a desktop machine is fine. SQL Server in Personal Mode would be ideal for a person that wants to archive everything, but does little reporting.

Please note: Genesis strongly recommends against attempting to use GenWatch3 on a laptop computer.

* If during the demo period the customer wishes to test the performance of an extensive report that will span all 60 days, then we highly suggest 2GB of RAM.