Transcript
Technical Release notes
iProtect™ Aurora 8.02
o System requirements o Highlights new version o New features in iprotect™
Publication January, 2015 Keyprocessor BV Paasheuvelweg 20 1105BJ Amsterdam www.keyprocessor.com Tel.: +31-20-4620700
This manual represents the knowledge at the above mentioned date. Keyprocessor works nonstop to improve her products. For the most recent technologic information please contact your consultant or dealer.
Content overview Publication .................................................................................................................... 2 Content overview .......................................................................................................... 2 1 Introduction ................................................................................................... 3 2 System requirements ....................................................................................... 4 2.1 Hardware (server) ....................................................................................... 4 2.2 Software .................................................................................................... 4 2.3 New Hardware ............................................................................................ 4 2.4 Licence .................................................. Fout! Bladwijzer niet gedefinieerd. 2.5 Browser support .......................................................................................... 5 3 Highlights iProtect™ 8.02 ................................................................................. 6 3.1 Added Menu items ....................................................................................... 6 3.2 Removed Menu items................................................................................... 6 4 New features in iProtect™ 8.02 ......................................................................... 7 4.1 Apollo support............................................................................................. 7 4.2 Support ASB CCS 7000 ................................................................................ 7 4.3 Analogue values (Sensors) ........................................................................... 7 4.4 Import Specified Sense Settings .................................................................... 9 4.5 Expand controlroom functions ....................................................................... 9 4.6 2 times presented card switch intrusion ..... Fout! Bladwijzer niet gedefinieerd. 4.7 Improved export function ............................................................................11 4.8 Colorized cards show card status ..................................................................11 4.9 Random pincode generation.........................................................................11
1
Introduction
These release notes provide information about all the new features of iProtect™ version 8.02. It will also give you information about the needed software/hardware environment which is necessary to install and run iProtect™ 8.02
2 2.1
System requirements Hardware (server)
The following servers can be updated to iProtect™ version 8.02: SUN X2270 DELL KP21 DELL KP22 DELL KP41 DELL KP42 Future servers
Note: it’s highly recommended to install a minimum of 4GB RAM in the iProtect™ server. Depended on type of server, the license and use of iProtect™ more memory may be required.
2.2
Software
The following software is needed to update/install iProtect™ version 8.02: Java 7 Tomcat 7 Linux ubuntu o 12.04 (iPuntu build 1.6.5 or Higher) All the files will be delivered on an installation CD-ROM or USB/Download via Customerportal.
2.3
New Hardware
Supported hardware in version 8.02: Apollo Controller ASB CCS7000 Intrusion Panel
2.4
License
iProtect™ will only use the major version number (8.02) to validate the license instead of the version number including the build number (e.g. 8.02.15). From iProtect™ version 7.0x.xx 8.00.xx 8.01.xx 8.02.xx
2.5
To iProtect™ version 8.02.xx 8.02.xx 8.02.xx 8.02.yy
New license needed Yes Yes Yes No
Browser support
The following browser types are supported in combination with iProtect™ Aurora version number: Mozilla Firefox = > 21.0 o Known issue: Media image player (video) Internet Explorer 9 Internet Explorer 10 Internet Explorer 11 Internet Explorer 12 Google Chrome
3
Highlights iProtect™ 8.02
The following highlights are introduced in iProtect™ version 8.02. Details will be given in the chapters below. Support Apollo Controller Support ASB CCS 7000 Intrusion Panel It is now possible to select specific Sense (Diva) cameras, Sense (Diva) procedures etc. that will be imported in iProtect (extra button on camera (presettings import) and external-NVR) Expand Control room functionality Activate or deactivate intrusion arming by offering the card 2 times at a reader Improved Export At card screen colorized cards show card status Random pin code generation
3.1
Added Menu items
Installation | Hardware | Analog input Installation | Hardware | Analog input type
3.2
Removed Menu items
Access | Management | Card | Reset place and APB. Access | Management | Delete Cards. These functions can now be done by multi-select on the cards.
4
4.1
New features in iProtect™ 8.02
Apollo support
An Apollo in combination with iProtect™ (Security Management System) offers you a complete solution for the monitoring of equipment for your critical locations/infrastructure. Think of Energy, Water, Data-centers, Telecom and other technical unmanned locations. Because the locations are unmanned, access control, alarm monitoring and environment conditions becomes very important. The Apollo can inter alia monitor the temperature, humidity and air flow but is also capable of smoke-, intrusion- and water detection in the cabinet. This monitoring is essential to increase the lifetime and reliability of the system and helps preventing malfunctioning, damage and reduces operational costs. The operator can fully control the cabinet remotely using iProtect™. iProtect is extremely suitable for monitoring a large amount of buildings, areas and cabinets. The Apollo also supports SNMP (Simple Network Management Protocol) for monitoring, in case iProtect will not be leading for monitoring the cabinet. The installation and configuration of the Apollo controllers is described in separate documents: Apollo Installation Manual, Apollo Technical Manual.
4.2
Support ASB CCS 7000
Because the end of (ISDN) digi access a new ASB security system is integrated in iProtect™. To replace the iProtect linked old ASB security systems. CCS7000 is designed specifically for professional projects. Dedicated modern design combined with smart individually programmable ambient illumination of keypad stations and access control readers make the system contribute to the beauty of its environment. Surface mounting or flush mounting models enable unobtrusive installation. Integrated IP and GPRS alarm transmission enables both single and dual path alarm transmission configurations. The integrated IP router and smart firewall enables redundant GPRS routing for IP enabled point of sale terminals.CCS7000 supports all market compatible detection devices including smoke detectors, both cabled or wireless. CCS7000 provides security to every high risk security project where compliance with EN50131/EN50136 is required.
4.3
Analogue values (Sensors)
With the introduction of the Apollo, iProtect can also receive analogue signals from sensors. These signals are defined as analog inputs. iProtect supports 2 types of analogue inputs: - kpSensor: which are sensors (temperature and humidity) that can be connected to the 1-wire bus on the Apollo - Analog inputs: which are internal sensors of the Apollo device and can measure board temperature, power levels, and power fuse status The figure below shows the settings for an analog input.
Important fields in the settings screen are: Type: This is the choice between kpSensor and Analog input Minimal Change: the minimal change in analogue value that has to occur before this changed value is logged in the database. This reduces the number of logged values in the database to only substantial changes. Beware: this value is defined in thousands of the actual value. In this example the minimal change is 1 degree Celcius. Unit: The unit type of the analogue value (temperature in degrees Celcius, Humidity in %, Power in Volts) Value: The actual value of the sensor in units. Sensor type: Defines what type of unit is measured. Analog input type list: A list of value ranges that can be used to define the state of the input (for example temperature too high). See next paragraph. The analog value type list is a list of intervals that can be defined to link an analogue value to a defined state. For example for the temperature, in the example above, we have defined 3 states: - Temperature low, from -2 C to 10 C - Temperature normal, from 10 C to 50 C - Temperature high, above 50 C
3 type elements are added to the analog value type element list: 1. Temperature low with a base value of 0
2. Temperature normal, with a base value of 10001 (= 10,001 C) 3. Temperature high, with a base value of 50001 (= 50,001 C) If the value of a sensor crosses the boundary between 2 ranges a transaction is logged indicating that the state of the analog input changed. With this mechanism it is possible to trigger actions when the temperature becomes too high.
4.4
Import Specified Sense Settings
The way that objects are imported from a Sense (former Diva) system has been changed. A Read in button is added to the node diag. By pressing this button all objects (cameras, layouts, presets, procedures and viewers) are read in from the Sense system and presented in a popup. You can now select which cameras, layouts, presets, etc. you want to import into the iProtect system by checking the appropriate boxes and pressing the add button. After this is done, the objects can be imported into the iProtect system by pressing the import button in the node dialog.
4.5
Expand controlroom functions
Now it is possible to receive selected events (not only alarms) from "slave" iProtect systems on the control room "master" iProtect™ when running a multi iProtect environment (license 5200). Whether a certain event is send to the control room iProtect system is determined by a setting in the Event notification definition dialog. If the checkbox Remote store is checked this event gets copied to the master system and appears in the event log of the master system.
In the serverlist on the master iProtect server you need to check the Store checkbox in the server settings of the slave system entry in order to receive the events from that slave system. Also the time zone of the slave system needs to be defined so the correct time transformation can be applied.
4.6
Arm intrusion by 2x card
A feature is add that makes it possible to arm an intrusion area by presenting the access card twice at the reader. This is only possible for readers that are linked to a security area and for access cards that have the right to arm a security area. This option can be enabled by a checkbox in the security area tab of a reader. When the checkbox Security armin the double card section is checked a second checkbox appears. This check box (Wait access till) determines whether to wait for the second time a card is presented before unlocking the door or that we should immediately unlock the door (normal situation). It might be necessary to check this box in cases that immediately unlocking the door causes problems (e.g. automatic doors).
4.7
Improved export function
In the export the value’s Startdate, Enddate, valid and unlimited are added, also multiple phone numbers and email addresses are exported.
4.8
Colorized cards show card status
Cards have a color: -a red card is not valid at the moment -a green is valid at the moment -a yellow is valid, but will expire in a specified amount of days(*) A little exclamation mark at a card indicates -a the card is not connected to a person -there is no cardgroup or individual reader attached to this card.
*This can be specified in “Installation-> settings-> general settings->card->Adjust icon color days before expiration”. (or in the same below a specified systemuser).
4.9
Random pincode generation
It’s is possible for a pincode cardcoding (manual cardnumber entry) to generate an automatically random cardnumber*. *Setting in “Installation-> settings-> general settings->card->Display button for next number” (or in the same below a specified systemuser) must be set (check box checked).
