This guide does not cover every aspect of the WatchManager software and/or setups. Additional online or telephonic support may be required.

Transcription

1 User's Guide This guide does not cover every aspect of the WatchManager software and/or setups. Additional online or telephonic support may be required. WatchManager Demonstration Data Installation 2014 Graham Smith & Associates All rights reserved Postnet Suite 10303, Private Bag X7005, Hillcrest, Peaceway Road, Drummond, KwaZulu Natal RSA Website -

2 Thank you for downloading the demonstration version of WatchManager V7.60 SQL Please read the BEFORE YOU INSTALL section to ensure that your PC meets the minimum required specifications, and that you have disabled any anti-virus/malware application that might prohibit the installation of WatchManager Graham Smith & Associates All rights reserved

3 Plea se note tha t this da ta is for testing purposes only! The dem onstra tion da ta ha s a 14 da y licence to a llow you to run "rea l tim e" scena rios in a test environm ent Plea se ensure tha t you ha ve dow nloa ded the correct version of the prog ra m using the link provided on our w ebpa g e WatchManager Download SELECT TH E FIRST LINK - D ow nloa d for new insta lla tion (includes Postg resq L) Sa ve the file to a folder on your PC. D o NOT select the RUN option. *** BEFORE YOU INSTALL *** The following hardware (PC) specifications are required : a minimum of 4GB memory a CPU (processor) that runs at 2.7ghz or higher a 500GB hard drive that runs at a minimum speed of 7200 RPM a RS232 serial port to connect the base/receiver AND the COM port numbers that Windows has assigned Any of the specifications lower than the listed, will affect the performance of WatchManager and will not give you the full benefit of all the features. Other hardware requirements : the manufacturer and model number of the base/receiver you will be testing the transmitter number/s of the radio/telephone/dual sim you will be using to test alarm signals Software : one of these Operating Systems - Windows 7 Professional / Windows XP SP3 / Windows Server 2003 or 2008 / Windows 8 anti-virus and malware software installed, must be disabled to allow a successful installation the Windows firewall must be set to allow all traffic from WatchManager on both public and private networks the Windows User Accounts Control settings must be set to NEVER NOTIFY Adobe Reader must be installed If you a re unsure of a ny of the a bove setting s/requirm ents, plea se conta ct your IT or W a tchm a na g er Consulta nt for a ssista nce 1

4 Go to the folder on your PC that contains the WM760.xxx(sql).exe file and click to install. (xxx is the current build number and will change as updates are added to the software) The installer will run for several minutes as files and databases are created. Please tick all the ACCEPT boxes. Once the installation has been completed, you will be presented with the WatchManager CONTROL CENTRE to continue setups. OV ERV IEW OF HOW W ATCHM AN AGER DEALS W ITH ALARM SIGN ALS There are 4 seperate processes that are used for the processing of signals coming in from your base/receiver, namely : CONTROL CENTRE FRONT END PROCESSOR (FEP for short) WMSERVER OPERATOR SCREEN The CONTROL CENTRE is responsible for the management of the system and, is also the management centre for the other 3 processes. The FRONT END PROCESSOR manages the communications between the RS232 COM port and your base/ receiver. The WMSERVER manages the interpretation of signals coming into the FRONT END PROCESSOR and, is responsible for sending these signals to the OPERATOR SCREEN. The OPERATOR SCREEN is the daily operational centre where signals are actioned by controllers, and, where customer maintenance/job carding/reporting is executed from. The OPERATOR SCREEN is the ONLY part of WatchManager that is used for daily operations. The other 3 are minimised and are only accessed by System Administrators for additional system settings. In a nutshell : The Control Centre opens or closes the FEP, WMServer and Operator Screen The FEP receives signals from the base/receiver and sends it to the WMServer for interpretation WMServer sends the signals to the Operator Screen for actioning so, it stands to reason that, if either the FEP or WMServer is NOT running, no signals will be received on the Operator Screen. 2

5 CONTROL CENTRE LOG ON AS ADMINISTRATOR (password 1234) EXIT CONTROL CENTRE TO SHUT DOWN WATCHMANAGER REOPEN WATCHMANGER FROM THE DESKTOP ICON AND LOG IN AS ADMINISTRATOR (password 1234) 3

6 Select SETUP, SECURITY TEMPLATES, MASTER USER. On the template screen, using the scroll bar to move down, change all ALLOWED options to Y (granting the Master User full access to the system) Close template screens to return to the Control Centre From the left hand menu, select MANAGE SQL SERVERS Highlight the entry WINXP-VM3 and select DELETE, OK to continue and close window to return to Control Centre. 4

7 PROGRAM STATUS AND CONTROL Select RUN for the 3 components Front End Processor, Operator Screen and WMServer. The 3 processes will start up and present you with the Operator Screen where you can once again log on as Administrator (password 1234) You will now have 4 icons on your Windows task bar which is as follows : Control Centre Front WMserv End Processor Operator Screen SET UP BASE/RECEIVER COMMUNICATIONS IDENTIFY THE INSTALLED COM PORTS THROUGH YOUR WINDOWS DEVICE MANAGER 5

8 Select the Front End Processor from the Windows task bar to open window. Log on as Administrator and select RECEIVER SETTINGS. Highlight one of the receivers and select CHANGE 6

9 Click on RECEIVERS to open a drop down box listing manufacturer and model number of base/receivers and, using the scroll bar on the right, find the receiver you will be installing and SELECT. Selecting the incorrect format will result in garbled data. Back on the Receiver screen, change the PORT NO to the number you identified in your Windows Device Manager. Change OPERATION to Y - normal operation. Leave all other fields as is and OK to close window. ALL LISTED PROTOCOLS ARE PRESET AS PER THE MANUFACTURER AND SHOULD THEREFORE NOT BE CHANGED AS THIS WILL RESULT IN GARBLED SIGNALS. Close all the Receiver windows to return to the Front End Processor. 7

10 TEST YOUR SYSTEM BY SENDING A FEW SIGNALS FROM AN EXTERNAL SOURCE. Once the signal is seen on the base/receiver, it should also appear in the Front End Processor. If the signals do not appear in the FEP, go back into the Receiver Settings and change the COM port number (assuming you have more than 1 COM port installed). Repeat the excercise until you see signals coming through into the FEP. If no signals are received into WatchManager, please contact your base/receiver consultant to check that cabling and setups are correct on the actual base/receiver itself. IMPORT EVENT CODES Select the OPERATOR SCREEN from the Windows Task Bar. Select MENU to open up settings (top right of Operator Screen) and Select GLOBAL EVENT CODES 8

11 Select IMPORT and find the relevant.sax file in the folder C:\WMWINSQL Double click to select the appropriate file and then OK to import the event codes. Certain formats, such as 4x2, do not have any standards and these codes would have to be added manually. Close Global Events and exit the Menu to return to the Operator Screen. 9

12 ADD TRANSMITTER NUMBER TO THE TEST CUSTOMER A test account has been set up to give you an example of the information required on customer records - i.e. keyholders/zones etc. Using this test account, add your transmitter number to ensure that signals received are not allocated to an UNKNOWN customer. Select CUSTOMERS from the Operator Screen icon bar at the top (left) Find the test customer and highlight. Select CHANGE On the MONITORING INFO tab, insert your transmitter number in 1st Monitoring Code and then select the correct SIGNAL DECODE for your event codes by using the drop down box. The 2nd Monitoring Code is only used for dual monitoring (eg Radio and Telephone) or where two different manufacturers are installed at the same client (eg FSK Radio and RDC GPRS) 10

13 OK to close record and exit the customer list. ************************************** The basic setups for testing are now complete and you can start receiving signals for controllers to action and check customer history etc. For a more detailed guide of each individual field/tabs on the customer record and other features, please download our USER GUIDE from the following link : W e look forwa rd to hea ring from you. CONTACTS 11

14 2014 Graham Smith & Associates All rights reserved. Product and company names mentioned in this manual may be trademarks or registered trademarks of their respective companies. Mention of third-party products is for informational purposes only and constitutes neither an endorsement nor a recommendation. The author assumes no responsibility with regard to the performance or use of these products. All understandings, agreements, or warranties, if any, take place directly between the vendors and the prospective users. Every effort has been made to ensure that the information in this manual is accurate. The author is not responsible for printing or clerical errors. The product described in this manual incorporates copyright protection technology that is protected by method claims of certain patents and other intellectual property rights. 12