ПопулярноеКак выбрать охранную сигнализацию Периметральная сигнализация – надежная охрана дома Сигнализации для охраны квартир Сигнализация с автозапуском Виды пожарно-охранных сигнализаций Беспроводная пожарная сигнализация Адресно-аналоговая пожарная сигнализация Методические материалы
Главная страница Security center software
2 3 4
Security Center software is designed to run under control of Microsoft Windows XP/Vista/7 operations systems. The server part of the Security Center software is recommended to run under control of Microsoft Windows Server 2003/2008 operational systems. It is necessary to note the following features of the Security Center software:
It consists of independent functional parts (modules) each one of which is designed to fulfill specific task. This on the one hand, permits to protect each module against possible failure of any other to the utmost level and, on the other hand, allows each module to be installed in a separate computer in a network.
It is oriented to work in a network which supports TCP/IP protocol. Thus any changes made in the system on any network computer are immediately applied to all software modules working in this network.
Operator rights are determined in relation to particular action in specific software module. Thus, the levels of operator access to both entire program and its separate components are implemented. For example, operator access both to entire Object Manager module and to the function of object security schedule editing only can be limited.
Receiving equipment of a central station makes possible to pick up and process events from control panels (hubs, object blocks) having built-in communicators (digital message transfer units - specialized modems). Depending on the control panel type, its functional and service capabilities, particular information about object status can be received from this panel. Most of control panels can transmit wide range of information. For example, these can be user data who performed arming or disarming; place (zone number) of alarm or failure (open or short-circuit); partial arming with indication of disarmed zones, etc. Due to this a feature duty operator of the complex has the most comprehensive information both about object status (armed, disarmed, alarm, etc.) and about equipment technical condition (battery discharged, missing 220V, telephone line failure, etc.)
Hardware system requirements
Minimum configuration: Intel® Pentium IV 2.4 GHz processor, RAM 2 Gb, 17 SVGA monitor, audio card, USB port for electronic security key installation.
Recommended configuration: Intel® Core i5 2.4 GHz processor, RAM 4Gb, 19 SVGA monitor, audio and network card for software operating in network, USB port for electronic security key installation.
Operational system requirements
The following operational systems are supported:
Microsoft Windows XP
Microsoft Windows Vista
Microsoft Windows 7
Microsoft Windows Server 2003
Microsoft Windows Server 2008
The Security Center software, version 3.4 is designed to be operated both with 32-bit versions and with 64-bit versions of mentioned operational systems.
Before the installation of the Security Center it is recommended to update operational system with the last of service packs offered by Microsoft company.
Electronic security key
The Security Center software is protected against illegal copying by an electronic security key. Prior to use the Security Center you should connect an electronic key to USB port of a computer and perform its driver installation.
The Security Center software is delivered in the following kit:
o Distributive of the Security Center full version, intended for installation the Security Center on a
new computer where this software has not been installed previously. o Distributive of the Security Center Service Pack, intended for upgrading already installed the
Security Center software (or Andromeda 2.8 software) to the Security Center version 3.3. o Distributive of electronic security key drivers.
The electronic security key installed in USB port of a computer.
Operational system selection
It is recommended to run the Security Center software under Microsoft Windows 7 operational system.
If the Security Center software is supposed to be used in a network, then the server part of the Security Center software installation (complete installation) is preferably to be executed on the computer running Microsoft Windows Server 2008 operational system.
Using NTFS as a file system would be the best choice.
It is strongly recommended to update running an operational system by installation of the last service packs offered by Microsoft.
Configuration of computers hard drive subsystem
To provide reliability of information storage and to increase system performance it is recommended to mount two hard disks in a computer in which full installation of the Security Center software will be executed. In this process, an operational system and executable files of the Security Center should be installed on one hard disk and database directory - on the other. If there is no possibility to mount two hard disks it is recommended to split a single hard disk into two sections and accommodate an operational system in one of them, and the Security Center database directory - in the other.
Additionally, irrespective of a disk subsystem configuration, it is necessary to set up the procedure of the Security Center software database backup so that backup copy would be created on an additional hard drive or network resource - physically other information storage device.
Before Security Center installation, please, make sure that Andromeda Liberty software or Andromeda software with version that is lower than 2.8 are not installed on your computer. If you find one of the abovementioned software, it is necessary to delete it before Security Center installation.
To install the Security Center it is necessary to have Microsoft Internet Explorer , version 8.0 or higher, software running in a computer. Also, it is recommended the following components and programs being available in the system:
Windows Installer, version 3.1 or higher.
Microsoft Data Access Components (MDAC), version 2.8 or higher.
Microsoft .NET Framework, version 2.0
Prior to starting the installation of the Security Center you should make sure that all hardware requirements and operational system requirements are fulfilled.
During the installation of the Security Center you should specify values for several installation parameters.
Immediately after the installation program start-up it is necessary to specify the installation program user interface language.
Then you will need to choose a language of the Security Center software user interface from the following list:
Be attentive: it is impossible to change the selected value after the installation. If a mistake is made during the user interface language selection then in order to correct it you will need to remove the Security Center software and install it once again.
Then the installation program will offer you to specify directory which will contain executable files of the Security
After this you need to choose the type of workstation to which the installation is executed:
Full installation should be chosen in case when a computer will execute the role of server: it will store the Security Center software database and also it will receive events.
In addition, the full installation should be chosen in case when this is the only computer which will run the Security Center software.
Microsoft SQL Server and the Security Center database will be installed on a computer during the full installation. Additionally, the Event Manager module will be installed on a computer. This module receives and processes events.
Installation on network workstation should be chosen in case when it is necessary to arrange a workstation in local computer network. At the network workstation, virtually all program functions are available for an operator. The exception is constituted by the number of service operations such as modification of the Event Manager settings and backup procedures management.
When the installation on network workstation is executed it will be necessary to specify a computer on which the full installation has been preliminary executed.
During the full installation, it will be necessary to specify directory where the Security Center software database will be stored.
To increase performance of the Security Center software it is recommended to place database files on a separate hard disk or at least in a separate section of the hard disk. By default the installation program prompts to install database files in a disk section other than a system section.
Also it will be needed to specify the necessity of BDE installation. BDE subsystem ( Borland Database Engine ) was used by the Andromeda software, versions 1.0 - 2.76, as well as the Andromeda Liberty software to organize access to database. Security Center software uses BDE subsystem when importing data from databases of mentioned programs only. If it is not necessary to import information from databases of the Andromeda software, versions 2.6 - 2.76 or the Andromeda Liberty then BDE subsystem installation is not required.
When the full installation has been performed the named instance of Microsoft SQL Server 2005 Express Edition software appears on a computer. The instance name is ANDROMEDA . To perform the full installation it is necessary that a computer does not contain the instance of Microsoft SQL Server with such name.
Installation on network workstation
When the Security Center software is installed on a network workstation it is necessary to specify the instance of Microsoft SQL Server software which is used to store database.
The instance of Microsoft SQL Server software is installed during the full installation of the Security Center . The name of instance being installed is ANDROMEDA. Thus, it is necessary to select from the list the string such as <computer name>\ANDROMEDA , where <computer name> is the name of a computer, on which the full installation of the Security Center software has been performed.
If the installation program could not find in local network the instance of Microsoft SQL Server software, which is used to store database of the Security Center we recommend to specify a computer name and an instance name manually.
Hereafter the installation program will require to enter the name or IP address of a computer on which the Event Manager module is started. In most cases this is the same computer which is used as the Security Center software server.
Connection with the Event Manager module is required for the rest of the Security Center software modules in order to exchange information and synchronize actions.
Problems during installation
If any problems have arisen during the installation of the Security Center software you should contact technical support service of C. Nord by telephone +7 (812) 327-16-36, by fax +7(812) 327-16-33 or e-mail email@example.com.
When you refer to technical support service you should specify the Security Center software version being installed and describe an arisen problem.
If you refer by e-mail we recommend to attach to your letter the archive containing files:
File C:\Andromeda Install.log
This file contains the Security Center installation program activity.
Log. files from C:\Andromeda Log folder
Files in this folder contain activity log of the Security Center modules.
Files from C:\Program Files\Microsoft SQL Server\90\SetupBootstrap\LOG folder
Files in this folder and its subfolders contain activity logs of Microsoft SQL Server program installation.
The listed files do not contain personal data or any confidential information.
Security Center editions
Andromeda Security Center is supplied in various editions. A100 and A600
These Security Center editions are designed to be operated with central surveillance units manufactured by Altonika Company.
А100 and А600 editions allow to use only those event sources, which are designed to receive events from
When you order Security Center , editions А100 and А600 , it is necessary to specify number of event sources from Lonta-202 or RS-200 . The number should correspond to number of units, which are supposed to be connected to Security Center .
Among themselves the editions differ the maximum possible number of serviced objects: no more than 100 objects for edition А100 and no more than 600 objects for edition А600 .
If while operating Security Center , edition А100 or А600 either the other central surveillance unit is required to connect or the number of serviced objects will exceed 600 pieces it is necessary to update the edition of Security Center to one of the standard.
Standard editions of the Security Center software differ the maximum possible number of serviced objects: 250,
500, 750, 1000, 1500, 2000 and so on.
There is no restrictions on usage of event sources, but event sources from central surveillance unit of other firms are purchased separately.
Purpose of modules
The Andromeda Security Center software consists of modules each one of which is designed to fulfill specific tasks.
The Event manager module serves to receive events from receiving equipment of a central station as well as directly from certain types of field equipment, e.g. via GPRS and Ethernet communication channels. In addition, it is just the Event Manager module where automated event processing takes place: event chains control, sending SMS messages and transmitting events to other systems.
It is necessary to note that the Event Manager is the interlink for all other modules of the Security Center : it should be started the first as it is the one via which other modules exchange information about new events, actions of operators and other changes which have taken place during module.
Using the Object Manager module new objects are created and descriptions of existing objects are changed.
The Duty Operator module is used by operator to process events. The main module functions are monitoring of operational status of objects, viewing the last received events, recording operator actions in response to alarms received from objects.
The Maps of Objects module is designed to create object approach schemes, floor plans and arrangement of security lines. Also, the Maps of Objects module is used to display object alarm loops on the floor plan when responding to alarm.
The list of Security Center operators as well as their rights in each of modules is established in the Personnel Manager module. In the same module, you can modify the list of response guards as well as the list of local network computers which run network workstations of the Security Center .
The Database Wizard is designed to fulfill the following operations:
database verification and error correction
restore database from backup copy
data import from the Andromeda software database, the Andromeda Liberty software, the Guardian
software and the CSM32 software.
data export from the Security Center database for using in other programs
In the module System setting you can modify reference guides which are used for the description of objects: list of event templates, event classes and actions connected with them, object types and list of additional properties.
The graphic object plan including the distribution of sensors as well as schemes of approaches to an object can be created or modified using Maps of Objects module.
To proceed to work you should start the Event Manager module and set up event sources - the special module components which serve to receive events from equipment of a central station.
Event sources setting is performed in the Event Sources window. To get access to this module you should select item Event Sources from the Event Manager module menu (right-click the icon in the system field of the taskbar).
If the Security Center is installed for familiarization purposes then to create events from objects you can use Emulate events from menu of the Event Manager .
After the Event Manager has been started you can proceed to work with other modules. You should enter objects into the system using the Object Manager and monitor events being received and respond to alarms using the Duty Operator .
The Andromeda Security Center contains the function to perform import of information about objects from databases of the following programs:
Andromeda , versions 2.0 - 2.76
If prior to the Security Center any software from above mentioned list was used, then for comfortable changeover to using the Security Center you can import object descriptions from a database of these programs.
If it is intended to import data from the Andromeda , versions 2.0 - 2.76, or the Andromeda Liberty software then during installation of the Security Center you should specify the necessity to install BDE as this very subsystem is used to access to these programs data.
Data import is performed using Database Wizard module. In case of importing data of the Andromeda , versions 2.0 - 2.76, or the Andromeda Liberty software all files from database folder will be required. When there is backup copy in ZIP format you need to extract files from the archive in any folder on a computer hard drive.
The Event Manager module is designed to receive events from receiving equipment of a central station as well as directly from certain types of field equipment, e.g. via GPRS and Ethernet communication channels. The result of processing the received events by Event Manager module consists in events which form the basis of the Security Center operation.
In the Event Manager the automated event processing takes place: event chains control, sending SMS messages and transmitting events to other systems.
The Event Manager is the interlink for all other modules of the Security Center : it should be started the first as it is the one via which other modules exchange information about new events, actions of operators and other changes which have taken place during module.
After module starting, in the system field of Windows task bar the icon appears which informs about the module operation. When any event is received the icon color changes, and if you move the cursor onto the icon the information about last event time and total number of events from module starting appears. Right-click on module icon results in the menu displaying.
You can get access to settings if you select Setting... item in the module menu.
The Frequency of security schedule alarms parameter sets the interval of system events with ZZXB and ZZXC codes generating. System events with these codes are generated when the daily object security schedule is violated and long-term object security is violated respectively.
Setting of security schedule as well as setting of long-term security of object is performed individually for each object in the Object Manager module.
The Interval of repeated events filtration parameter sets the interval within which the second and succeeding equal events received via different communication channels will be considered being repeated. The repeated events are processed in the Security Center modules in a special way. For instance in the Duty Operator module, they are not displayed in the general list of received events. But they can be included in the display of events from the object tab. In addition, the repeated events are not included in event reports unless such necessity is specified intentionally.
Recommended value for this parameter is 60 seconds.
Test events filtration can be turned off using homonymous parameter. When filtration is turned on the test events are processed in the same manner as the repeated events: they are not displayed in the Duty Operator module and in the event reports.
It is essential to understand that the repeated and test events constitute 75 to 95 percents of total number of events received by the Security Center . Consequently repeated and test events filtering mechanism permits to release the Security Center operators from necessity to process useless information. For the same reason events filtration positively influence the performance of the Security Center modules. It is not recommended to turn off repeated and test events filtration without strong reasons.
The Backup tab of the Event Manager module settings window is intended for management of backup tasks. There are two different types of the Security Center database backup copies: operative and full.
Full database copy contains all information being stored in the database at the moment of copying including received events, operator actions and sent SMS messages for all time of software running.
Data amount in the operative copy is much less: in this copy the events, operator actions and SMS messages for the last month only are stored.
In general, it is recommended to use operative copying for backup tasks. Full backup is recommended to be executed manually or using tasks of Windows scheduler.
For each backup task several destination folders can be specified: after backup copy of data has been created it will be copied in each of these folders. In this process the number of the Security Center database backup copy files in each destination folder will be supervised. If during backup copy creation it is determined that the number of backup copy files is greater than specified by the Number of files in the destination folder parameter then the oldest file of backup copy is deleted.
In addition to the backup interval, which sets the frequency of executing the backup task you can set the start time for a task executing. In such manner you can arrange a backing up once a day or start a periodic backing up each day at the same time.
More detailed information about backing up can be found in the respective section of description of Database Wizard module one of the purposes of which is creation of the Security Center database backup copies.
The main purpose of the Event manager module is to receive events from receiving equipment of a central station as well as directly from certain types of field equipment, e.g. via GPRS and Ethernet communication channels. Variety of methods and protocols for annotations transmission is supported using special components of the Event Manager module which are called sources of events.
You can get access to event sources settings by selection of the Event sources... item in the module menu. The Security Center software, version 3.3, contains the following sources of events:
Event source from PimaGuard
It is designed to receive events via serial port or Ethernet from Mcard for MS-DOS , Pima NetSoft and PimaGuard for Windows software in the Andromeda protocol.
It is the most advanced source for receiving events from a central station receiving equipment from Pima company. In case when support of the latest capabilities of a central station receiving equipment, as well as protocols and events transmission channels is required this very event source should be used. When source from PimaGuard is used in the mode of receiving events via Ethernet, we recommend to use separate instance of event source for each instance of transmitting software.
Event source via TCP/IP
It is designed to receive events via network supporting TCP/IP protocol form the following equipment manufactured by C-Nord company:
o GSM transmitters: TP-100GSM and TP-100GSM II - via GPRS channel
o panic button Button - via GPRS channel
o Cepheus extender - via Ethernet channel When this event source is used usually dedicated IP address in the Internet is required. Additionally, it is recommended to connect different types of equipment to different instances of event source, and when the Cepheus extender is connected the best variant is to use a separate instance of event source for each extender.
2 3 4