*iProtect™ Guarded Area
- Tom Polman
- Arnout van Wanrooij
Installation Manual | IM-20210309-TP-13 iProtect Access / Security | Functionalities |  |
|
- 1 1 Introduction
- 2 2 Guarded area
- 3 3 Guarded area setup in iProtect
- 3.1 3.1 License
- 3.2 3.2 Add Guarded area group
- 3.3 3.3 Scenarios
- 3.4 3.3.2 Scenario 2: Guarded area with local third-party input and cardreader
- 3.5 3.3.3 Scenario 3: Guarded area linked to an access control area
- 3.6 3.3.3.1 Alarm user Group and admittance
- 3.7 3.3.3.2 Card reader
- 3.8 3.4 Add inputs to Guarded area
- 3.9 3.5 Add outputs
- 4 4 Keymap
This manual represents the knowledge at the above-mentioned time. TKH security works non-stop to improve her products. For the most recent technical information please contact your consultant or dealer.
1 Introduction
This document describes the guarded area(s) functionality of iProtect™. This functionality was introduced with iProtect version 8.03.
1.1 Functional description
The purpose of a Guarded area is to monitor a group of inputs e.g. detectors, door contacts, passive infrared
detectors, smoke detectors, etc.
Arming and disarming the guarded area goes as far as possible without additional or conscious acts of the
'users'. Therefore, the Guarded area functionality is perfectly suited for manned- and unmanned sites or
places.
The system will always arm, even with failures. The system will automatically omit the input with a problem but can also be omitted by the user. All omits will be displayed and events/alarms will be send and stored in
iProtect™.
The most distinctive difference between a modern intrusion system and Guarded area (iProtect™) is the
combination with access control. Instead of using Keypads, iProtect™ is using the access control reader to
arm and disarm the area.
When a system is armed but the iProtect™ administrator wants to open the door to enter this area, the Guarded area will be switched off automatically and the door will go open.
Guarded area functionality is available when the system is online- or offline situation. That means that it is
functioning independently of the connecting status (e.g. network failure) with the iProtect™ database. The
operation of access control and intrusion functionality remains as it was and the user will not notice a network failure.
All the generated events will be stored locally and pushed to iProtect™ when the connection is established.
1.2 System setup
The Guarded area system setup is schematically processed in the drawing below:
The Orion and the Apollo supports resistor measurement (analog values). Other devices only support digital inputs.
For more information about the Apollo or Orion, please consult the technical documentation.
2 Guarded area
This chapter will describe the settings which can be made into iProtect™.
2.1 Guarded area group
Menu: Installation | Hardware | Alarm system | Guarded area group
Definition
You can add one or multiple Guarded areas to "Guarded area group". By doing this it is possible to monitor
several guarded areas with one operation.
Function
Only the data which is necessary to setup ‘Guarded area’ will be described.
Status
Alarm | Active when one of the Guarded areas has occurred an alarm |
Alarm count | Number of counted alarms |
Disarmed | Active when one of the Guarded areas is disarmed. |
Disarmed counts | Number of disarmed counts |
Too long disarmed | Active when one of the Guarded areas is disarmed too long |
Long disarmed count | Number of too long disarmed counts |
Partly armed | Active when one of the Guarded areas is still armed |
Partly armed count | Number of partly armed counts |
Manually omitted | Active when one of the Guarded areas is armed with a manual omit |
Manually omitted count | Number of manually omitted counts |
Tampered areas | Active when one of the Guarded areas has a physical tamper status |
Tampered inputs countv | Number of tampered input counts |
2.2 Guarded area
Menu: Installation | Hardware | Alarm system | Guarded area group | Guarded area
Definition
A Guarded area is used to monitor multiple inputs, assigned to a group (Guarded area). Multiple areas can be created from the same line or different lines.
Function
Only the data which is necessary to setup ‘Guarded area’ will be described.
Mode | Set or Unset the alarm manually |
Line | Specific line for this Guarded area |
Status | When arming- or disarming the Secured area, different statuses will be returned. Below the |
Disarmed | System is turned off. |
Arming | Walk out time has started, system is going to Arm. |
Partly armed | System is armed but with one or more Omitted inputs |
Walk in | User gets time to unset the armed area. When Walk in time has |
Alarm | One of the inputs has been activated while the area is armed. |
Too long disarmed | When ‘Auto arm’ is enabled and when there is no input change during |
Event to database
Ready to set event | Ready to set event will be send during this Time zone |
Input status event | Input status event will be send during this Time zone |
If no timezone is selected the events will always send to the database.
General
Camera | Camera which is logical connected to the Guarded area |
Set/Unset input | Set/Unset the Guarded area using an (third party) input |
Unset Reader | Unset the Guarded area using a local card reader |
Area | Unset the Guarded area using a local card reader(s) connected to the area. |
Walk in time | Time to enter the Area without generating an alarm (hh:mm:ss) |
Walk out time | Time to leave the Area without generating an alarm (hh:mm:ss) |
Auto arm¹ | When active, the system will automatically Set the Guarded area |
Auto arm time¹ | The time that no events occur, the system will arm automatically (hh:mm:ss) |
Pre-arming alarm buzzer¹ | When active, the reader buzzer will be active during the Prearming |
Pre-arming warning time¹ | The time frame before the walk-out time will be active (hh:mm:ss) |
Max. unset time | send an event to the operator that the system is still unset |
Max. alarm buzzer time (sec) | If an alarm occurred, the maximum buzzer time |
The “Unset reader” setting does not need any additional configuration (see chapter 3,3), the cards with access rights on the reader unset the area.
The Area setting needs additional configuration (see chapter 3.3.3), you must specify who is allowed to unset the area, with this option you are able to setup access rights with and without disarm rights.
Status
Last mode change | Last time of mode change |
Last disarm | Last time area was disarmed |
Manually omitted | Manually set the Omit by the Input |
Reset alarm memory | If an input caused an alarm, the user can check the specific inputs |
Tampered inputs | If an input is tampered but also omitted, it will be displayed |
Mute | In the event of an alarm while the system is unset, the user has the ability to deactivate either the buzzer alarm or the siren output alarm, or both |
Alarm notification
Buzzer when disarming | The buzzer of the card reader will be active during disarming |
Buzzer arming | Buzzer of the card reader will be active during arming |
Alarm buzzer | Buzzer of the card reader will be active during an Alarm |
Show guarded area status on LED | LED of the card reader will be blinking when armed |
¹: See chapter 2.2.1
2.2.1 Example: Timing diagram
2.3 Reader behavior vs set and unset
Depending on the state of the reader the behavior is defined as follows:
Reader status is ‘office’, Guarded area is going to set
Response:
Reader status will change from ‘office’ to ‘normal’
o Door closesReader goes to status ‘armed’
Reader status is ‘open’, auto-arm time has ended
Response:
The Guarded area will not set (waiting sequence) as long the reader is in status ‘open’. One of the
reasons could be:
o Reader mode set by operator to ‘open’
o by reader input (door in latch mode)
o when current status is open (by automatic latch)
Response when the reader mode ‘open’ is changed to normal/automatic/closed etc.
the pre-arming sequence will be started directly
Guarded area status ‘Armed’ and a reader is set to ‘Open’
Response:
The reader status will not change to status ‘Open’ until the guarded area is unset. One of the reasons
could be:
o Reader mode set by operator to ‘open’
o by reader input (door in latch mode)
o when current status is open (by automatic latch)
Reader status ‘armed’ and unlatched once by operator
Response:
Connected guarded area will unset
Reader goes to the defined status (e.g. normal, open, blocked etc.)
Door will be unlatched once, during the unlatch time
Reader status ‘emergency’, Guarded area is going to Set
Response:
Reader status will stay in ‘Emergency’
Door stays open
2.4 Guarded area input
Menu: Installation | Hardware | Input
Definition
An “Input" interprets incoming (contact) signals of an "Controller" from periphery parts like sensors, detectors, smoke detectors etc.
Function
Only the data which is necessary to setup ‘Guarded area’ will be described.
Handling
Input mode | Follow input signal | the input follows the status of the contact signal |
Type | Normally open | Normally open |
| Normally closed | Normally closed |
| Blocked | The input has no function and will not work |
| EOL | End Of Line* |
| DEOL | Dual End Of Line* |
| DEOL inverted | Dual End Of Line inverted* |
| TEOL | Triple End Of Line inverted* |
| TEOL inverted | Triple End Of Line inverted* |
*Recommended resistor values: EOL: 4k7 or 5k6 and Masking 22K
Digital I/O status
Activated | Yes | Input is enabled |
| No | Input is disabled |
Status
Omit | Off | Input takes part of Guarded area |
| On | Input does not take part of Guarded area |
Physical | Unknown | No status known |
| Tamper short circuit | Depending on the used input type, a Tamper or |
| Low resistance circuit | Will not be used |
| Closed circuit | Depending on the used input type, an Closed |
| High resistance circuit | Will not be used |
| Open circuitWill not be used | Depending on the used input type, an Open circuit |
| Detector masked | Depending on the used input type, an Detector |
| Tamper circuit voltage | Will not be used |
| Detector error | Will not be used |
Logical | Unknown | No status known |
| Tamper | Depending on the used input type, an Alarm has |
| Idle | Depending on the used input type, the input is idle |
| Holdup alarm | When the input occurred and alarm, the alarm will |
| Local alarm | Depending on the used input type, a Local alarm |
| Omitted | When the input is Omitted (bypassed) |
| Active | Depending on the used input type, the input is |
| Automatically omitted | Active when input is omitted by system |
Guarded area
Guarded area | When a Guarded area is selected, the Input takes part of the Guarded area functionality |
Last Omit status change | The last Omit status change |
Input has caused an alarm | If an input caused an alarm, the value will be ‘true’. The user can reset the alarm memory manually |
3 Guarded area setup in iProtect
This chapter will describe the settings which has to be made into iProtect™.
3.1 License
No extra licenses are needed when programming Guarded area’s into iProtect™.
3.2 Add Guarded area group
Click in iProtect™ Aurora on the menu item Installation | Hardware | Alarm system | Guarded area
group.Right-click in the browse window and select ‘Guarded area group’. The detail window opens.
Enter these data:
Name: Enter a logic name
Save the data.
3.3 Scenarios
Click with you right mouse button on the created “Guarded area group” (see chapter 4.2) and choose
“Add Guarded area”. The detail window opens.Enter the following data:
Name: Enter a logic name
Mode: unset
Line: select a specific Line for that specific Area
Unset reader: select a specific Reader which will unset the Area.
Walk-in time: Enter time which is needed.
Walk-out time: Enter time which is needed.
Auto arm: (check)
Auto arm time: Enter time which is needed
Max. unset time: Enter time which is needed
Buzzer when disarming: Check if needed
Buzzer when arming: Check if needed
Alarm buzzer: Check
Show guarded area status on LED: Check if needed
Max. alarm buzzer time (sec): 180 (seconds)
Save the data.
To link Inputs to the Guarded area, see chapter 3.4
To link create outputs on the (guarded area) line, see chapter 3.5
3.3.2 Scenario 2: Guarded area with local third-party input and card
reader
Click with you right mouse button on the created “Guarded area group” (see chapter 4.2) and choose
“Add Guarded area”. The detail window opens.Enter the following data:
Name: Enter a logic name
Mode: unset
Line: select a specific Line for that specific Area
Input: select an input, connected to the Third-party system (to set and unset the area)
Reader: select a specific Reader (optional)
Walk-in time: Enter time which is needed
Walk-out time: Enter time which is needed
Auto arm: (check)
Auto arm time: Enter time which is needed
Max. unset time: Enter time which is needed
Buzzer when disarming: Check if needed
Buzzer when arming: Check if needed
Alarm buzzer: Check
Show guarded area status on LED: Check if needed
Max. alarm buzzer time (sec): 180 (seconds)
Save the data.
When the Guarded area setup is finished, one output and three inputs have to be defined to get more feedback from the systems.
To link Inputs to the Guarded area, see chapter 3.4
To link create outputs on the (guarded area) line, see chapter 3.5
3.3.3 Scenario 3: Guarded area linked to an access control area
Click with you right mouse button on the created “Guarded area group” (see chapter 4.2) and choose
“Add Guarded area”. The detail window opens.Enter the following data:
Name: Enter a logic name
Mode: unset
Line: select a specific Line for that specific Area
Area: select an Access area (to set and unset)
Walk-in time: Enter time which is needed
Walk-out time: Enter time which is needed
Auto arm: (check)
Auto arm time: Enter time which is needed
Max. unset time: Enter time which is needed
Alarm buzzer: Check
Max. alarm buzzer time (sec): 180 (seconds)
Save the data.
To link Inputs to the Guarded area, see chapter 3.4
To link create outputs on the (guarded area) line, see chapter 3.5
3.3.3.1 Alarm user Group and admittance
The alarm user Group determines whether the user may arm or disarm the Guarded area.
Open in iProtect™ Aurora the menu item Installation | Hardware | Alarm system | Third party | Alarm
user group. The detail window opens.Enter the following data:
Name: Enter a logic name
Arm: check if allowed to arm the Guarded area
Disarm: check if allowed to disarm the Guarded area
Save the record.
Click in the browse window and click the plus sign of the ‘alarm user group’ and select 'Area list'. Check
the desired area(s) and save.Open in iProtect™ Aurora the menu Access | Settings | Admittance to add the Alarm user group to an
existing AdmittanceSave the record
3.3.3.2 Card reader
Open in iProtect™ Aurora the menu item Installation | Hardware | Reader.
Select a card reader which will be used to arm or disarm the security area. The detail window opens.
Open the Tab Security Area:
Show security area status on LED: Select a desired security area
< The LED from the card reader will blink when security/guarded area is Armed>
Arm security/guarded area: Select a desired security area
Disarm security/guarded area: Select a desired security area
Save the record.
3.4 Add inputs to Guarded area
Click in the browse window (tree-view) and click the plus sign of the ‘Guarded area’. The 'Input list' will
be displayed. Check the desired inputs and save.Open in iProtect™ Aurora the menu item Installation | Hardware | Input or click with you right mouse
button on the created Node (see chapter 3.3) and choose “Add input”. The detail window opens.Enter the following data:
Name: Enter a logic name
Input mode: Follow contact signal
Type: See chapter 4.4
Bypass: Off
Guarded Area: Select the Guarded area
Save the record.
3.5 Add outputs
Click in iProtect™ Aurora on the menu item Installation | Hardware | Output.
Right-click in the browse window and select ‘Add output’. The detail window opens.
Enter these data:
Name: Enter a logic name for the output
Node: Select a Node which is on the same Line as the Guarded area.
Output mode: Follow source
Source: Follow guarded area status
Mode: Disarmed, Alarm, Armed, Arming, Partly armed, Pre-arming signal
auto arming, too long disarmed or Walk in
Source: Follow guarded area mode
Mode: Set or Unset
Source: Follow Guarded area alarm buzzer
Save the data.
4 Keymap
Table: GUARDINGAREA
Column: | NAME | Description for guarding area |
| HOLDALARM | Boolean signaling that there is or has been an alarm [to be |
| MODE | Guarding mode |
| READYTOSET | All inputs in area are inactive or bypassed |
| STATUS | Current area status |
| SUPPRESSTAMPER | Boolean when activated to 'omit' all tampered inputs |
| TAMPERINPUT | This guarding area has tampered input(s) |
| MANUALLYOMIT | This guarding area has manually omitted input(s) |
Table: ALARMINPUT
Column: | NAME | Description for input |
| ACTIVE | Kept for backward compatibility, will be removed in future |
| LOGICALSTATUS | Logical status of input |
| OMIT | Omit status of input |
| HOLDALARM | Hold alarm till reset by guarding area |
| ALARMSTATUS | Boolean if (AlarmCount <> 0) |
| PHYSICALSTATUS | Physical status of input |
Table: ALARMOUTPUT
Column: | NAME | Description for output |
| ACTIVE | Is output active or inactive |
| ALARMSTATUS | Boolean if (AlarmCount <> 0) |
| GUARDINGAREAMODE: | If source = 15 (Follow guarding area mode), output is active |
| GUARDINGAREASTATUS: | If source = 14 (Follow guarding area status), output is active |