EBI R610.1 ID - Guide

EBI Temaline Interface
Intrusion Detection Module Guide
Release 610
Document Release Issue Date
800-00443 610 - 6.1 1 June 2021
Notice
This document contains Honeywell proprietary information. Information
contained herein is to be used solely for the purpose submitted, and no part of this
document or its contents shall be reproduced, published, or disclosed to a third
party without the express permission of Honeywell S.r.l.
While this information is presented in good faith and believed to be accurate,
Honeywell disclaims the implied warranties of merchantability and fitness for a
purpose and makes no express warranties except as may be stated in its written
agreement with and for its customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential
damages. The information and specifications in this document are subject to
change without notice.
Copyright 2021 – Honeywell S.r.l.
Training classes
Honeywell holds technical training classes on Enterprise Buildings Integrator.
These classes are taught by experts in the field of building control systems. For
more information about these classes, contact your Honeywell representative.
Compliance
To obtain applicable EU compliance Declaration of Conformities for this product,
please refer to our website, https://extranet.honeywell.com/HBS/EBI/EBIHOME/
Pages/default.aspx.
For any additional information regarding the compliance of this product to any
EU-specific requirements, please send email to [email protected]
Related documentation
For a complete list of publications and documents for Enterprise Buildings
Integrator, see the Enterprise Buildings Integrator Overview.
2 www.honeywell.com/buildingsolutions
Contents
1 Introduction 7
Related documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
2 Intrusion configuration overview 11

Intrusion subsystem architectures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Tema ID architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Tema SEC architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Intrusion system composition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Access the intrusion configuration displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
EBI toolbar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Navigation pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Work with the configuration displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3 Intrusion 19
Plants display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Open the Plants display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Plants - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Plants - Security tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Plants - Feedback tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Plants - Supervision tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Plants - Alarm Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Plant duplication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Credential Types display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Open the Credential Types display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Reading technologies managed by intrusion detection . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Define the credential type for intrusion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Intrusion Zones display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Open the Intrusion Zones display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Intrusion Zones - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Intrusion Zones - Arm/Disarm tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Zone management types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Intrusion Zones - Test tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Intrusion Zones - Others tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Intrusion Zones - Supervision tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Intrusion Zones - Alarm Settings tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Logics display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Open the Logics display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Logics - Main tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3
CONTENTS
Logics - Configuration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Logics - Behavior tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Logics - Supervision tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Logics - Alarm Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Example of logical correlation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Save data for several logics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Operative Notes display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Open the Operative Notes display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Operative Notes - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4 Hardware Configuration 43
TemaServer display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Open the TemaServer display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Configure a TemaServer for intrusion detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
LonWorks ring connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Overview of ring configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Inserting RTUs into the ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
.................................................................. 50
Memory Formatting display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Open the Memory Formatting display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configure memory formats for intrusion detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Default intrusion database format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
RTUs display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Open the RTUs display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Configure an RTU for intrusion detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
RTU types managed by the intrusion detection module . . . . . . . . . . . . . . . . . . . . . . . . . 57
Miniterminals display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Miniterminal types and composition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Open the Miniterminals display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Miniterminals - Main tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Miniterminals - Activation tabs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Miniterminals - Supervision tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Miniterminals - Alarm Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Detectors display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Open the Detectors display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Detectors - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Detectors - Detector Type tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Description of detector types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Detectors - Behavior tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Detectors - Feedback tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Detectors - Supervision tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Detectors - Alarm Settings tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Save data for several detectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Intrusion Digital Output display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Open the Intrusion Digital Output display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
CONTENTS
Intrusion Digital Output - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Intrusion Digital Output - Supervision tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Intrusion Digital Output - Alarm Settings tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5 Administration 77
Typologies Configuration display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Open the Typologies Configuration display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Typologies Configuration - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Typologies Configuration - Status tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Typologies Configuration - Alarm tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Typologies Configuration - Command tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Create a custom typology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Peripheral profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Open the Peripheral Profiles display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Peripheral Profiles - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Create a new peripheral profile starting from a default one. . . . . . . . . . . . . . . . . . . . . . . 84
Peripheral operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Open the Peripheral Operators display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Peripheral Operators - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6 Point detail displays - ID 89

Using point detail displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Layout of point detail displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Access a point detail display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Point Detail display - TemaServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
TemaServer PDD - General tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
TemaServer PDD - Recent Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
TemaServer PDD - Firmware tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Uploading the TemaServer database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Point Detail display - Plant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Plant PDD - General tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Plant PDD - Recent Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Plant PDD - Plant Zones tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Point Detail display - Miniterminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Miniterminal PDD - General tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Miniterminal PDD - Recent Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Point Detail display - Detector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Detector PDD - General tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Detector PDD - Recent Events tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Point Detail display - Output Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Output Device PDD - General tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Output Device PDD - Recent Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Point Detail display - Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Zone PDD - General tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Zone PDD - Recent Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5
CONTENTS
Point Detail display - Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Logic PDD - General tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Logics PDD - Recent Events tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
7 Statuses, Commands, and Events 109

TemaServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
TemaServer statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110
Commands on the TemaServer ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113
Events generated by the TemaServer ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115
Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Plant statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117
Commands on the Plant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Events generated by the Plant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118
Miniterminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Miniterminal statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Commands on the Miniterminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Events generated by the Miniterminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Detector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Detector statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Commands on Detectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Events generated by Detectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Output device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Output Devices statuses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Commands on Digital Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Events generated by Digital Outputs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Intrusion Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Intrusion Zone statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Commands on Intrusion Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Events generated by Intrusion Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Logic statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Commands on Logics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Events generated by Logics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
8 Conformity to the CEI 79-2 Rules 135

Introduction
1
This guide is designed for operators who are responsible for configuring and
managing the optional Intrusion Detection module for the Temaline Interface
subsystem. For an overview of the system see “Intrusion subsystem architectures”
on page 12.
Topics include:
Chapter Contents See

Intrusion configuration Description of intrusion subsystem page 11
overview architectures, and how to access and work
with the intrusion configuration displays
Intrusion The displays used for the logical page 19
configuration of the intrusion module:
Plants, Credential Types, Intrusion Zones,
Logics, Operative Notes, Peripheral
Calendar, Feedbacks, Scheduled
Commands
Hardware Configuration The displays used for configuring the page 43
physical devices that make up the
intrusion detection system:
TemaServers, Groups/Lines, Memory
Formatting, RTUs, Miniterminals,
Detectors, Intrusion Digital Outputs.
Administration The displays for configuring various page 77
functions relating to rights, storage and
utilities:
Summary Point Creation, Typologies
Configuration, Historical Data Storage,
Sites, Stations, Peripheral Operators,
Peripheral Profiles
7
1 – INTRODUCTION
Chapter Contents See

Point detail displays The displays used for operating the page 89
intrusion detection subsystem. These
allow you to monitor and interact with
dynamic objects, for example running
commands or configuring parameters
Statuses, commands and The complete list of statuses, commands, page 109
events and events associated with all the objects
managed by the intrusion detection
module
RELATED DOCUMENTATION
Related documentation
In addition to this guide, you may consult the following manuals provided with
the Temaline Interface subsystem (of which the Intrusion Detection module
constitutes an integrated, optional module):
• MT Display – User Manual—Help on using the Man-Machine Interface of the
Intrusion Detection Module
• Temaline Access Control Configuration Guide—Provides easy-to-follow
examples and tutorials on configuring functions for the access control, time
and attendance and security system
• Temaline Interface – Installation Manual—Provides instructions on installing
the subsystem
For further information on using the station and on managing the alarm list, see
the documentation that is provided with EBI Enterprise Buildings Integrator.
9
1 – INTRODUCTION
Intrusion configuration
overview 2
The Intrusion Detection (ID) module is an option integrated into the Temaline
Interface subsystem. It is used to configure, via the Temaline Interface's displays,
the Tema ID panels which manage the intrusion detection peripheral devices, i.e.
detectors, actuators, and all Man-Machine Interface peripheral devices.
This module allows the enhanced management of the Intrusion Detection matters
and provides many different modes for arming /disarming of the zones; it also
enables you to create correlations between detectors so that an alarm can actually
be raised (logics).
This chapter provides information on the supported intrusion architectures, and
how to access and work with the configuration displays for intrusion detection.
Topic See
Intrusion subsystem architectures page 12
Access the intrusion configuration displays page 15
Work with configuration displays (common operations) page 17
11
2 – INTRUSION CONFIGURATION OVERVIEW
Intrusion subsystem architectures

This section illustrates the peripheral architectures supported by the Temaline
intrusion detection module, the connection between the TemaServer and the
supervision center, and the field devices utilized
• For intrusion architectures based on TemaServer ID, see “Tema ID
architecture” on page 12.
• For intrusion architectures based on TemaServer SEC. See “Tema SEC
architecture” on page 13.
Tema ID architecture
The figure below illustrates the peripheral architecture using the TemaServer ID.
Note:
• You can use two types of connections for communication with the supervision
center (LAN for the primary connection and modem connection as a backup
line).
• By default, the Tema ID panel is equipped with 16 inputs and 16 configurable
outputs, plus two outputs whose behavior is preset (general alarm relay and
general failure relay); it also enables you to connect other I/O devices or
interface devices using a LonWorks network.
• You can also connect the I/O devices to the ID Panel using a ring (see
“LonWorks ring connection” on page 47).
INTRUSION SUBSYSTEM ARCHITECTURES
Tema SEC architecture

The peripheral architecture using the TemaServer SEC is illustrated below:
Note:
• Tema SEC enables you to connect I/O or interface devices using a Lonworks
network.
Intrusion system composition

The following table summarizes the features of the intrusion detection subsystem
in terms of number of inputs/outputs and miniterminals that are allowed. These
values apply to both TemaServer ID and TemaServer SEC solutions.
Component Max. Notes

Nr.
RTU: 63 Types of allowed RTUs:
C02 - Q0x - B0x - K00 - A10 -
A11
Max. Nr. RTU Q0x 1 You can increase the number of RTUs
Q0x by decreasing other types of RTU.
Max. Nr. RTU A10 / RTU A11 60
Miniterminals: 5 These RTUs are not into the ring, but they
Keyboard (K00), Readers come from the ring.
(B0x) and MT display (C02)
13
Component Max. Notes

Nr.
Max. Nr. MT display 2
Detectors 240 Connected to the 60 RTUs A10 / RTU
A11
Digital outputs 240 Connected to the 60 RTUs A10 / RTU
A11
Alarms that are managed using 100 After this number is reached, old alarms
the alarm list of MT display will be canceled.
ACCESS THE INTRUSION CONFIGURATION DISPLAYS
Access the intrusion configuration displays

The configuration displays for the intrusion detection module can be accessed
from the EBI toolbar or from the left-hand navigation pane as shown below. Some
of these displays are specific to intrusion detection (for example, Miniterminals
and Intrusion Zones) while others are in common with access control (for
example, TemaServers and RTUs).
EBI toolbar
1 From the EBI toolbar, select Menu > Configure > Temaline Intrusion
Detection >...
2 Select the desired grouping: Hardware Configuration, Intrusion, or
Adminstration...
3 And finally select the desired display.
Navigation pane
Once you open an intrusion detection display as described above, an Intrusion
Configuration navigation pane appears on the left from which you can access all
the intrusion detection displays.
1 In the navigation pane, expand the desired grouping (such as Hardware
Configuration or Intrusion).
15
2 Click the desired configuration display.
WORK WITH THE CONFIGURATION DISPLAYS
Work with the configuration displays

General information about how to work with the configuration displays and
perform common operations is provided in:
• Access Control Configuration Guide, section Configuration Displays
Reference > Common Operations.
To open this documentation from the EBI station help:
1 In the EBI menu select Help > Temaline Reference > Access Control
Configuration Guide > Configuration Displays Reference > Common
Operations.
2 From here, you can access the following:
Topic Explains how to...

Open an existing element • Select the object to open in a configuration
display, either directly from a list, or using the
Search feature
Configure elements • Create an object from scratch (New button) or
starting from an existing one (Duplicate button)
• Delete an object (Delete button)
• Modify the ID of an object
• Modify multiple objects at the same time (Save
all elements button)
• Work with the pharmaceutical option when
modifying objects
Filters • Apply/remove or configure filters to work with
only a subset of the objects in a display
List navigation • Sort lists or tables in configuration displays
based on different column headers
• Horizontally scroll through the headers of wide
lists
• Page backwards and forwards through long lists
• Type in a few characters to quickly find the
desired item in a list
Horizontal tab scrolling • Horizontally scroll the different tabs in a display
Enter times and dates • Use the time and calendar controls
Alarm settings • Set alarm priorities in the Alarm Settings tab of
a configuration display
17
Topic Explains how to...

Supervision settings • Associate an object with displays and signatures
in the Supervision tab of a configuration
display.
Time zone settings • Specify the time zone used to synchronize the
date and time.
Intrusion
3
The Intrusion group comprises displays for the logical configuration of the
Intrusion Detection module.
To learn about Go to:

Plants display page 20
Credential Types display page 26
Intrusion Zones display page 28
Logics display page 36
Operative Notes display page 41
Peripheral Calendar display for these displays, refer to:
Feedbacks display • Temaline Access Control Configuration Guide,
Scheduled Commands display section Configuration Displays Reference >
Access Control Definition > ...
19
3 – INTRUSION
Plants display
The term Plant, or more specifically, Intrusion Detection Plant, refers to the
portion of the intrusion detection subsystem controlled by a Tema ID Panel.
From the physical point of view, the plant is composed of detectors and actuators,
concentration and feed devices, and human-machine interfaces. (For further
information on using the peripheral interface, see the MT Display – User Manual
which is provided the Temaline Interface Intrusion Detection module.)
From the logical point of view, the plant is made up of various zones subjected to
control, which therefore allows for a global management.
Furthermore, the plant allows for the performing of operations that affect all
objects making up it.

Open the Plants display page 20
Plants - Main tab page 20
Plants - Security tab page 22
Plants - Feedback tab page 22
Plants - Supervision tab page 23
Plants - Alarm Settings tab page 23
Plants duplication page 24
Open the Plants display

• From the EBI toolbar: Select Menu > Configure > Temaline Intrusion
Detection > Intrusion > Plants.
• From the Intrusion Configuration navigation pane: Select Intrusion >
Plants.
Plants - Main tab
Field Description
Identification
PLANTS DISPLAY
Field Description
Brief The brief name of the plant (max. 4 characters). It is
used for the duplication of the whole plant.
It defines the rule to follow while assigning the
acronym to the objects that make up the plant to be
duplicated; i.e., the brief name of the plant must also
be part of the acronym of each object. For further
information, see “Plant duplication” on page 24.
Acronym The unique identifier for the plant. The acronym can
be made up of a maximum of 8 alphanumerical
characters (letters from A to Z, or numbers from 0 to
9.) If a Brief name has been assigned to the plant, the
acronym starts (first 4 characters) with the Brief
name.
To modify an existing acronym, double-click in the
field.
Point ID The identifier of the point used in the EBI
environment. It is automatically filled with the value
of the Acronym field and then, if required, you can
modify it (up to 40 characters). This field must be
unique.
Description A description of the point (up to 132 characters). Only
32 characters are sent to the peripheral level.
Free note Free notes on the plant.
TemaServer The TemaServer ID or TemaServer SEC controlling
the plant
Calendar The peripheral calendar used by the plant. See:
• Temaline Access Control Configuration Guide,
section Configuration Displays Reference >
Access Control Definition > Peripheral
Calendar display.
Operative note The operative note associated with the plant. See
“Operative Notes display” on page 41
Location
Sites
Facility Shows the reference to the Facility model item (up to
255 characters). Used for segregation purposes. You
can also fill in the field manually with an enterprise
model item.
21
3 – INTRUSION
Plants - Security tab
Field Description
Duress Password The password used to log in to the plant when under
threat.
Duress feedback The feedback that is activated in case of login to the
plant when under threat.
Duress profile The profile associated with the operator to log in to
the plant when under threat.
Auto logout after The timeout for automatic session closure (logout) of
the peripheral miniterminal (expressed in minutes).
(See “Miniterminals display” on page 58.)
Plants - Feedback tab
Field Description
Plant in alarm fbk, The feedback that is executed if at least one alarm has
not been acknowledged by the operator in a zone of
the plant.
Return The feedback that is executed when all alarms have
been acknowledged in all zones of the plant.
Plant in tampering fbk. The feedback that is executed when a tamper or
failure situation is detected within the plant, for
example, a cut or short of a detector, or a failure of
other devices.
Return The feedback that is executed upon return of all
failure situations in the plant.
Armed The feedback that is executed when all zones in the
plant are armed.
Disarmed The feedback that is executed if at least one zone in
the plant is in disarmed status.
Maintenance start The feedback that is executed when the maintenance
work mode has been set for the plant, meaning the
mode that is used while installing or maintaining the
plant.
Maintenance stop The feedback that is executed upon the end of the
maintenance work mode for the plant.
PLANTS DISPLAY
Field Description
Start running test fbk. The feedback that is executed when the general
testing mode has been set for the plant, meaning the
mode used when you test the whole plant after
installing and configuring it.
Stop running test fbk. The feedback that is executed at the end of the general
testing mode for the plant.
For further information on the possible work modes
for the plant, see Point Detail display - Plant.
Plants - Supervision tab

The Supervision tab associates the Plant with displays and signatures. For details
about these fields, refer to:
• Access Control Configuration Guide, section Configuration displays
reference > Common Operations > Supervision settings.
Plants - Alarm Settings tab

The Alarm Settings tab lets you configure what alarms are generated by the Plant,
and their priorities. For details about these fields, refer to:
reference > Common Operations > Set alarm Priorities.
23
3 – INTRUSION
Plant duplication
This function allows you to duplicate simultaneously all of the objects that belong
to the plant. A copy of all records, as well as all related references and
associations, is created.
To do this, you must first assign to the plant a unique brief name which identifies
it as a model. You must then integrate this brief name in each acronym assigned to
the objects that make up the plant (i.e., detectors, digital outputs, zones, logics,
miniterminals, RTUs, operative notes, and feedbacks).
This is essential for the duplication to work properly. In fact, the system creates a
copy of all records that relate to the objects making up the plant by replacing the
brief name currently on the acronym, or reference, with the new brief name that
identifies the new plant.
Considerations
The system verifies the uniqueness of the brief name of the plant, then it creates
the new plant using the old plant as a model. To duplicate the objects that belong
to the plant when you are creating an identical new plant, the system replaces the
brief name in each acronym with the new brief name of the new plant;
consequently, it updates all references and associations, setting both the new
belonging plant and the new TemaServer ID.
If a problem arises during duplication (for example, if an object exists whose
acronym does not contain a brief name to be replaced), an error message is
displayed.
Prerequisites
• You have configured a TemaServer ID for managing the new plant.
• You have assigned a unique brief name to the plant to be duplicated.
• You have entered the brief name of the plant in the acronym of all objects that
belong to the plant to be duplicated.
To duplicate a plant:
1 Select the plant to be duplicated, then click on Duplicate.
By default, the Only this record option is selected. This option allows you to
duplicate only the plant record, without duplicating its objects.
2 Select The whole plant.
3 In the Brief box, type in the new brief name (4 characters) which identifies the
new plant. This name will be used to replace the brief name that is currently in
the acronym of the objects that belong to the plant being duplicated.
4 Complete the Acronym of the new plant. The brief name has been
automatically entered in the acronym.
PLANTS DISPLAY
5 In the Description box, type in a description for the new plant.

6 From the TemaServer drop-down list, select the TemaServer ID that you have
created for managing the plant.
7 Click OK.
25
3 – INTRUSION
Credential Types display

The Intrusion Detection module allows you to perform various operations on the
system using card reader devices. Using a personal card allows you to quickly log
in to the MT Display, and to perform some commands.
To define the encoding format, you must establish the position and the size of the
fields (in characters or in bits) that are checked by the miniterminals. In addition,
the storage technology may affect the overall size of the layout.

Open the Credential Types display page 26
Reading technologies managed by intrusion detection page 27
Define the credential type for intrusion page 27
Tip
For a detailed description of the fields in this display, and full instructions on how to
configure them, refer to:
• Access Control Configuration Guide, section Configuration Displays Reference >
Access Control Definition > Credential Types display.
• In the EBI menu select Help > Temaline Reference > Access Control Configuration
Guide > Configuration Displays Reference > Access Control Definition >
Credential Types display.
Open the Credential Types display

Detection > Intrusion > Credential Types.
Credential Types.
CREDENTIAL TYPES DISPLAY
Reading technologies managed by intrusion detection

The table below shows the reading technologies that the Temaline Interface
Intrusion Detection module can manage, together with the related peripheral
devices.
Technologies of reading RTU Reader
Magnetic Trace II (ISO 7810) RTU B01
Schlumberger / Incard Smart Card (ISO 7816) RTU B03
Proximity UNIQUE RTU B04
HID Proxy RTU B07-B19
Smart Card ISO 14443A / B (MIFARE / ST) RTU B12
Define the credential type for intrusion

For step-by-step instructions and configuration examples, refer to:
• Access Control Configuration Guide, section Configure a Temaline System
> Configure the Credential Type > Examples of Credential Types
configuration.
27
3 – INTRUSION
Intrusion Zones display

Intrusion zones are aggregations of detectors and are characterized by a
homogeneous management mode, whether in terms of typology (for example,
vault, cash dispenser) or in terms of functional behavior (for example, all anti-
theft button).
The Temaline Interface subsystem allows you to configure up to 128 zones on the
system.
Specifically, the configuring of zones allows you to perform the global arming or
disarming of all of the detectors associated with those. Further, you can associate
actuation devices or logics with each zone in such a manner that the alarm
conditions indicated by the detectors or by the logics become real alarms only if
the associated zone is in the armed status. Otherwise, the alarm conditions are
filtered.
In summary, you can use this display to:
• set the management modes for the zones, in terms of arming/disarming
• set the execution of the test on the zone
• set the management of overtime for the zone
• define feedbacks to be executed following specific conditions
This display can also be accessed directly during configuration of the module,
that is, from any displays allowing selection or association of a zone, by double-
clicking on the box.
To learn about Go to
Open the Intrusion Zones display page 29
Intrusion Zones - Main tab page 29
Intrusion Zones - Arm/Disarm tab page 30
Intrusion Zones - Test tab page 32
Intrusion Zones - Others tab page 34
Intrusion Zones - Supervision tab page 34
Intrusion Zones - Alarm Settings tab page 35
INTRUSION ZONES DISPLAY
Open the Intrusion Zones display

Detection > Intrusion > Intrusion Zones.
Intrusion Zones.
Note: When you are configuring a zone, note that the selection combo box and all
selection lists display only those records that are in accordance with the
operator’s enterprise model.
Intrusion Zones - Main tab
Field Description
Identification
Acronym The unique identifier of the zone within the system.
The acronym can be made up of a maximum of 8
alphanumerical characters (letters from A to Z, or
numbers from 0 to 9).
field.
Point Name The identifier of the point used in the EBI
unique.
Plant The plant to which the zone to be configured belongs.
Location
Sites
model item. (In this case the item has to be written as
an existing complete path.)
29
3 – INTRUSION
Intrusion Zones - Arm/Disarm tab

This tab allows you to define the mode and the schedule plan for arming (i.e.,
activating the alarm detection) and disarming (i.e., deactivating the alarm
detection) the zone.
Field Description
Zone management type The drop-down list contains the five modes for
arming the zone:
• Manual
• Automatic
• Automatic with manual disarm
• Semiautomatic
• Confirmable
“Zone management types” on page 31 summarizes
the functioning of the various modes and indicates the
fields on the display used for their relative settings.
Arm Delay Timeout, in minutes, that elapses between the arm
command and the effective change of status for the
zone. This allows the person who has armed the zone
to exit the controlled areas.
Schedule grid
Start The start time of the first time period for disarming
the zone.
Stop The end time of the first time period for disarming the
zone, following which the zone is re-armed.
Resume The start time of the second time period for disarming
the zone.
End The end time of the second time period for disarming
the zone, following which the zone is re-armed.
Day Framework Allows you to select the days on which to schedule
the arm/disarm operation; that is, the days of the week
(from Monday to Sunday), the holidays, and the
special days. To select a day type, click the
corresponding box.
Alternate Schedule Allows you to define an alternative schedule program.
This is composed of two time periods and start and
end dates, which define the interval of days on which
to apply the given time period.
Field Description
Break overtime Allows you to set the overtime for the zone, meaning
to prolong the instance Stop of the planned time
periods which are used for disarming the zone,
expressed in minutes. If, for example, the time period
starts at 08:00 and stops at 13:00, and you enter in this
field a value equal to 15, the zone is automatically re-
armed at 13:15 rather than at 13:01.
End overtime Allows you to set the prolonging of the instance End
of the planned time periods used for disarming the
zone, in minutes.
Max time for manual disarm The maximum duration of the manual disarm,
expressed in minutes. Once this amount of time has
elapsed, the zone will automatically be rearmed.
• Used for Manual and Automatic with manual
disarm arming modes.
Time window for disarm The time, in minutes, within which the manual disarm
must be performed or confirmed.
• Used for Semiautomatic and Confirmable
arming modes.
Zone management types
Zone management type Example

Manual
Within the defined schedule program, the zone may be Start > 08:00 Stop > 13:00
manually armed/disarmed (from the miniterminal or Resume > 15:00 End > 18:00
from the graphic page).
On the specified days, the zone
• You can define a maximum time for manual (initially armed) can be manually
disarming (Max time for manual disarm), after disarmed/armed within this
which time the zone is automatically rearmed. period of time, and it will
• You can also manage the zone in a completely automatically be rearmed at
manual mode, independently of the time periods, 13:01 and at 18:01.
by setting to 00:00 both the Start Time and End
Time.
Automatic
The arming/disarming of the zone occurs
automatically, based on the scheduling of days and
time periods.
• You cannot manually disarm a zone that has been
put into an armed status automatically.
31
3 – INTRUSION
Zone management type Example

Automatic with manual disarm
The arming/disarming of the zone occurs
automatically, based on the scheduling of days and
time periods.
• You can manually disarm a zone that has been put
into an armed status automatically.
Semiautomatic
The zone can be manually disarmed at the beginning Start > 08:00 Stop > 13:00
of the given time period (Start or Resume), within the Time window for disarm = 05
established lapse of time (Time Window for m
Disarm), and then later be automatically rearmed.
There are two scenarios: On the specified days, the zone
(initially armed) is automatically
• If the operator does not perform a manual disarm disarmed at 08:00, but if the
within the established lapse of time, the zone operator does not confirm the
remains armed; disarming before 08:05, it is
• If the disarm is performed within the established automatically rearmed. In any
time, the zone is automatically rearmed at the end case, the zone is re-armed at
of the time period (Stop or End). 13:01.
Confirmable
The zone is disarmed automatically based on the Start > 08:00 Stop > 13:00
hourly scheduling, but the actual disarming is subject Time window for disarm = 05
to confirmation by the operator at the beginning of the m
time periods defined (Start or Resume), within the
time interval (Time Window for Disarm), which is On the specified days, the zone
established. There are two scenarios: (initially armed) can be manually
disarmed/armed before 08:05,
• If the operator does not confirm the disarm within and it will automatically be
the established lapse of time, the zone is rearmed at 13:01.
automatically rearmed;
• If the disarm is confirmed, the zone is disarmed
until the end of the time period (Stop or End) and
then automatically rearmed.
Intrusion Zones - Test tab
Field Description
Automatic test before the arm of Enables/disable automatic test on the zone, that is, on
the zone all detectors associated with that, before arming it.
Field Description
Arm the zone also if test is failed Enables/Disables the zone arming even if the test has
not been passed.
The figure below illustrates the various scenarios in
which at least one detector in the zone is in alarm
status, in accordance with the settings of the two
fields above:
Test start feedback The feedback when the test on the zone begins.
If desired, you can double-click these fields to open
the display to configure a feedback.
Test end feedback The feedback when the test has been completed.
Test failed feedback The feedback if the test does not succeed (i.e., if at
least one detector is in alarm status and the option
Arm the zone also if test failed was not selected).
Test OK feedback The feedback if the test succeeds and if the option
Arm the zone also if test is failed is selected.
33
3 – INTRUSION
Intrusion Zones - Others tab
Field Description
Max number of detectors The maximum number of detectors associated with
simultaneously disabled the zone that may be simultaneously disabled.
Parameter 1 General parameter for classifying the zone.
Parameter 2 General parameter for classifying the zone.
Operative note The operative note associated with the element. If
desired, you can double-click this field to show the
Operative Notes display display (see page 41), which
allows you to configure them.
If desired, you can double-click these fields to open
the display which then allows you to configure a
feedback.
Detectors in alarm feedback The feedback when there is at least one detector in the
zone in an alarm status.
Return detectors in alarm The feedback upon return of all alarm conditions in
feedback the zone.
Detectors in failure feedback The feedback when there is at least one detector in the
zone in a fail/tamper status.
Return detectors in failure The feedback upon return of the fail/tamper status for
feedback detectors in the zone.
Arm notice feedback The feedback when the zone arming starts if an arm
delay has been set for this zone (see Arm Delay
above).
Arm Feedback The feedback when the zone is armed.
Disarm Feedback The feedback when the zone is disarmed.
Prealarm Feedback The feedback when there is at least one detector in the
zone in a prealarm status.
Prealarm Return Feedback The feedback upon return of all prealarm conditions
in the zone.
Intrusion Zones - Supervision tab

The Supervision tab associates the intrusion zone with displays and signatures.
For details about these fields, refer to:
Intrusion Zones - Alarm Settings tab

The Alarm Settings tab lets you configure what alarms are generated by the
intrusion zone, and their priorities. For details about these fields, refer to:
35
3 – INTRUSION
Logics display
A logic is a procedure that correlates the statuses of several detectors with time
(logical correlation) and thereby provides a logical filter for the alarms generated
by the system, to reduce the number of false alarms.
In fact, if the detectors are associated with a logic, they do not directly generate
alarms, rather, they refer them to the logic to which they pertain. This latter
utilizes the criteria defined on this display to manage the emission of alarms.
This display allows you to:
• associate a maximum of 240 detectors with the logic;
• specify the number of detectors within the given logical correlation that must
be in alarm status, either simultaneously or not, to cause an alarm status for
the logic;
• specify the time to be utilized for the correlation.
The acknowledgment of a logical alarm produces the alarm return and resets the
logic status. To manage the alarms, the Logic must be armed and the associated
zone, if any, must be armed.

Open the Logics display page 36
Logics - Main tab page 37
Logics - Configuration tab page 37
Logics - Behavior tab page 38
Logics - Supervision tab page 38
Logics - Alarm Settings tab page 39
Example of logical correlation page 37
Save data for several logics page 39
Open the Logics display

Detection > Intrusion > Logics.
Logics.
Note: When configuring logics, the selection combo box and all selection lists
display only those records that are in accordance with the operator’s enterprise
model.
LOGICS DISPLAY
Logics - Main tab
Field Description
Identification
Acronym The unique identifier of the logic within the system.
The acronym can be made up of a maximum of 8
alphanumerical characters (letters from A to Z, or
numbers from 0 to 9.)
field.
unique
Description A description of the logic (up to 132 characters). Only
Plant The plant to which the logic to be configured belongs.
Typology The logic typology, meaning the possible statuses,
events, and commands for the object.
All objects have a default typology, and this may be
customized for the case of detectors and logics. The
default value is LOGIC (that is, the default typology
for logics), but the drop-down list contains the custom
configurations, if any (see “Typologies Configuration
display” on page 78).
Location
Sites
Logics - Configuration tab

This tab enables you to define the detectors to consider for the logical correlation,
and to establish the time interval to be utilized. For a practical example, see
“Example of logical correlation” on page 39.
37
3 – INTRUSION
Field Description
Time window The time, in seconds, that must elapse between the
first and second alarm signals before the alarm status
for the logic is generated.
Detectors focused Number of detectors that must be in a state of alarm,
even not simultaneously, to generate the alarm status
for the logic.
Available This area shows the acronym and description for the
detectors configured for the plant. To insert a detector
into the logical correlation, select it, then click .
To remove it, click .
Assigned This area shows the acronym and description for the
detectors that are considered for the logical
correlation.
Logics - Behavior tab
Field Description
Feedback on alarm The feedback when an alarm is generated.
Feedback on alarm return The feedback upon return of the alarm condition.
Zone The zone to which the logic is associated. The alarm
conditions detected by the logic become real alarms
only if this zone is inserted.
To configure zones refer to “Intrusion Zones display”
on page 28.
Operative note The operative note associated with the element. To
configure them, refer to “Operative Notes display” on
page 41.
Logics - Supervision tab

The Supervision tab associates the logic with displays and signatures. For details
about these fields, refer to:
LOGICS DISPLAY
Logics - Alarm Settings tab

llogic, and their priorities. For details about these fields, refer to:
Access Control Configuration Guide, section Configuration displays reference
> Common Operations > Set alarm Priorities.
Example of logical correlation

The figure below illustrates an example of the settings used when a logic
generates a logical alarm when two or more detectors (among those inserted into
the Assigned list to be considered for the correlation) go into alarm status within
a span of 10 seconds.
Save data for several logics

The Save all elements button allows you to modify at the same time one or more
parameters for all logics currently in the list. This means that you can modify
multiple logics at the same time.
1 If required, apply a filter so that the selection list at the top includes only the
logics to which you want to apply the changes.
2 Select the logic you want to use as a template, and make any required changes
to its fields.
3 Click Save all elements.
4 In the Save all elements dialog box, select the check boxes for the fields
whose configuration you want to copy to all the other logics.
5 Click Save selected. The selected fields are copied to all the logics currently
in the drop-down list at the top.
39
3 – INTRUSION
For more information refer to:

reference > Common Operations > Configure elements > Modify multiple
elements at the same time.
OPERATIVE NOTES DISPLAY
Operative Notes display

Operative notes are string messages of a technical nature that can be associated
with objects, to be displayed on the miniterminal of the Intrusion Detection
module. The notes convey information to the operators during alarms
management.
Open the Operative Notes display

Detection > Intrusion > Operative Notes.
Operative Notes.
Note: When configuring operative notes, the selection combo box and all
Operative Notes - Main tab
Field Description
Acronym The unique identifier for the operative note within the
system. The acronym can be made up of a maximum
of 8 alphanumerical characters (letters from A to Z, or
numbers from 0 to 9.)
field.
Note The text of the operative note.
Plant The plant for which the operative note is being
created.
Sites Select a valid plant to see the default site
41
3 – INTRUSION
Hardware Configuration
4
The Hardware Configuration group comprises displays for configuring the
physical devices that make up the Intrusion Detection system.
TemaServers display page 44
Groups/Lines display Temaline Access Control Configuration Guide,
section Configuration Displays Reference >
Hardware Configuration > Groups/Lines display.
Memory Formatting display page 51
RTUs display page 55
Miniterminals display page 58
Detectors display page 63
Intrusion Digital Outputs display page 72
43
4 – HARDWARE CONFIGURATION
TemaServer display
This display allows you to perform the physical configuration of the
TemaServers, the peripheral controllers that are responsible for managing the
field devices of the intrusion detection subsystem.
You can:
• define channels and connection modes to the Supervision Center;
• configure the connection modes with RTU components;
• define the time zone to be used;
• set visibility parameters on the TemaServer ID or TemaServer SEC for system
operators.

Open the TemaServer display page 44
Configure a TemaServer for intrusion detection page 45
LonWorks ring connection page 47
Tip
Hardware Configuration > TemaServer display.
Guide > Configuration Displays Reference > Hardware Configuration >
TemaServer display.
Open the TemaServer display

Detection > Hardware Configuration > TemaServer.
• From the Intrusion Configuration navigation pane: Select Hardware
Configuration > TemaServer.
TEMASERVER DISPLAY
Configure a TemaServer for intrusion detection

In the TemaServer configuration display you can set up the TemaServer to use for
intrusion detection.
Prerequisites
• You properly set the installation parameters of the TemaServer (IP addresses,
groups, LonWorks domain, and so on) using the TEMA Virtual Monitor. See
Access Control Configuration Guide, section Configure a Temaline System
> Configure the TemaServers > Configure the TemaServer1.
Procedure
1 Select Intrusion Configuration > Hardware Configuration > TemaServer.
2 Enter the Acronym and Description for the TemaServer.
3 From the TemaServer Type drop-down list, depending on the desired
configuration (see “Intrusion subsystem architectures” on page 12), select one
of the following:
• TS ID01 - TemaServer ID.
• TS SE01 - TemaServer SEC.
4 From the Group drop-down list, select the group that you set using the TEMA
Virtual Monitor. The selected group determines the connection mode (LAN
and/or PPP dial-up) used to communicate with the Supervision Center.
5 Select the Communication enable check box.
6 Select the Networking tab.
7 Under Ethernet, enter the IP address of the TemaServer. This is the same one
that was set using the TEMA Virtual Monitor.
8 In the LonWork area, specify the type of connection to be established
between the TemaServer and the peripheral RTU devices. There are two
possible options:
• Bus Typology—Normal Echelon connection type (default setting).
• Ring Typology—(available only for TemaServer ID) Connection between
the TemaServer and its RTUs utilizing an FTT LonWorks ring bus. The
connection between the TemaServer and its RTU devices can be
maintained even when there is a short circuit or a cut in the cabling.
9 If you selected the Ring Typology option, the Ring Configuration button is
enabled. This allows access to a window where you can configure the RTU
components to be inserted into the ring.
• For instructions see “Inserting RTUs into the ring” on page 50.
45
10 If the Group selected in the Main tab used PPP as the primary or backup
connection, a Dial-up tab appears, which enables you to configure the PPP
dial-up connection between the TemaServer ID and the Supervision Center.
• For instructions refer to the Access Control Configuration Guide, section
Configuration Displays Reference > Hardware Configuration >
TemaServer display > TemaServer - Dial-up tab.
11 Select the Behavior tab.
12 From the TemaServer DB Formatting drop-down list, select Intrusion. For
more information about this format, and how to customize it, see “Memory
Formatting display” on page 51.
13 Configure the remaining fields as required. For details refer to the
documentation referenced above.
Note: Control Zone Groups, Maintain Cardholder zone after failure, Feedback
on startups and antipassback are not used for intrusion detection.
14 Click Save.
TEMASERVER DISPLAY
LonWorks ring connection

This section provides an overview of the ring typology configuration and its
behavior, as well as instructions on how to configure it in the TemaServer
configuration display.
Overview of ring configuration

The figure below illustrates a ring configuration in which a TemaServer ID
communicates with its RTUs via a LonWork network in ring typology:
• The TemaServer ID can communicate with the RTU components in both

directions of the ring, by periodically commuting the direction. This allows
the system to maintain active communications and to perform verifications of
the operational status of the devices (polling activity).
• The RTU A10 devices used for the ring connection are equipped with an
internal switch whose closure can be requested by the TemaServer, meaning
that they are capable of physically opening the ring if a short circuit is
detected.
Therefore, the system is able to detect a cut or short situation in the ring and,
operating on the direction of communications and on the RTUs switches, can
restore the best communication condition.
47
Cut condition
During polling, one or more RTUs may not respond, but these may be reached
when the TemaServer changes direction on the ring. Because of this, it is possible
to identify a cut in the ring even preceding the first RTU that did not respond:
In this example, RTUs 3, 4, and 5 are reached normally, while RTUs 1 and 2 do
not respond. These are reached, however, when the TemaServer changes direction
on the ring.
Behavior in cut condition

• The TemaServer locates the cut between RTU 2 and RTU 3 and emits an
alarm; if its configuration has been so designed, it will also run a feedback
program.
• The TemaServer continues communicating with the RTUs in the ring, using
both directions, until the cut situation is resolved.
TEMASERVER DISPLAY
Short condition
Upon detecting a short condition, the RTUs open their internal switch.
The TemaServer emits an alarm and, if so configured, it executes a feedback

program.
It must furthermore determine and isolate which segment has the short circuit,
and then rebuild the ring without the short-circuited segments:
• It sends a command to close the internal switch of the first RTU on the ring
that responds, i.e. it closes it, so as to re-establish communications in that
segment of the ring.
• The TemaServer proceeds closing all of the switches, one by one, until it
closes the short circuited segment; this will cause a new opening of all of the
switches in the ring.
• The TemaServer places the last RTU that has been closed among the devices
to be excluded from the ring.
• The TemaServer proceeds, using both directions of the ring, closing all of the
internal switches, with the exception of those belonging to the RTUs that
delimit the short circuited segment.
• At this point the TemaServer may perform the binding procedure for all usable
RTUs on the ring.
The resumption of normal operation after a short circuit is performed manually
via the re-binding of the TemaServer.
49
Inserting RTUs into the ring

1 In the configuration display of the TemaServer ID, select the Networking tab.
2 Click the Ring Configuration button. This button is enabled when the
LonWorks Ring Typology option is selected.
• A window opens where you can specify which RTUs to insert into the
ring. The list on the left shows all the RTU A10 components managed by
the TemaServer ID.
3 For the RTUs related to I/Os that are managed internally by the TemaServer
ID, and which do not have to be inserted into the ring:
• Select them one at a time and click the button to insert them into the
RTUs not in the ring area.
• If necessary, use the button to remove components.
4 Similarly, for the RTUs to place in the ring:
• Use the arrow buttons to insert them in the RTU Position in Ring area.
• Use the and buttons to modify the position of the RTU within the
ring.
The positioning sequence of the RTUs in the ring must be correct to ensure
that the system works properly.
5 Click Save.
MEMORY FORMATTING DISPLAY
Memory Formatting display

The supervision center downloads into the memory of each TemaServer the
database tables necessary for the operation of the subsystem (for example, records
related to Miniterminals and RTU components managed by the TemaServer,
events data, and so forth).
The memory formatting display enables you to customize the format (number of
records) of these database tables.
This section presents only the Intrusion default format pertaining to the intrusion
detection module. For information about other database formats provided by
Temaline Interface, refer to the Access Control Configuration Guide.

Open the Memory Formatting display page 51
Configure memory formats for intrusion detection page 51
Default intrusion database format page 52
Tip
For a detailed description of the fields in this display, full instructions on how to configure
them, and information about other database formats, refer to:
Hardware Configuration > Memory Formatting display.
Guide > Configuration Displays Reference > Hardware Configuration > Memory
Formatting display.
Open the Memory Formatting display

Detection > Hardware Configuration > Memory Formatting.
Configuration > Memory Formatting.
Configure memory formats for intrusion detection

In the Memory Formatting configuration display you can modify the number of
records used in the database tables for intrusion detection.
51
1 Select Intrusion Configuration > Hardware Configuration > Memory

Formatting.
2 From the drop-down list at the top, select the default format that you want to
customize. In this case: Intrusion.
3 Click Duplicate. This enables you to use the default intrusion format as a
basis from which to modify the number of records.
4 Enter a new Description for the customized format.
5 The Configuration area lists the database tables that make up the selected
default format (see “Default intrusion database format” on page 52):
• The Default column shows default number of records in each table.
• Click in the Custom field corresponding to the table for which you want to
establish a new number of records, then type the new number of records.
6 Click Check to verify the compatibility of the data inserted with the number
of memory banks available. The resulting value is displayed in the Free Bank
(ram/flash) field.
7 If this value is negative (preceded by a minus sign), you must either decrease
the number of records of some unused tables or reduce the maximum number
of behavior models. The number of free banks must be positive; if you attempt
to continue with a negative value, you will get an error message when you try
to save and you will not be able to continue.
8 Click Save.
9 field.
Default intrusion database format

The default formats refer to the three archive types provided by Temaline
Interface:
• Buffers—Areas in the memory where data are stored that need to be used
later. Buffers contain information that must be sent to the host and saved even
when the communication between the Center and the peripheral devices has
been interrupted. In this way, all information is stored and extracted in the
same order as the related events have occurred (Events and Alarms). Data are
stored in a flash EPROM.
• Global Tables—These tables contain all data related to TemaServers
configuration. These are usually changed by the Supervision Center. Data are
stored in a flash EPROM.
• Dynamic Tables—These tables contain data that are frequently updated by
the TemaServer. These are stored in the RAM and are lost in the case of power
MEMORY FORMATTING DISPLAY
supply failure or TemaServer reset. Usually, they contain data on object

statuses.
This section describes in detail the database tables that are downloaded from the
supervision center to the peripheral level, as shown on this display, that is,
according to the default settings, once the Intrusion format has been selected.
The table names, the description, and the default number of records for each
database table are provided below.
Table 1 Database format for Intrusion Detection Module
Table Description Number of Notes

records
ALARMLIS The buffer where all events and alarms 100
are stored.
ICTUNODE Table containing TemaServers 512
identification data.
IDEFLOGI Table containing logics configuration 128
data.
IDETLOGI Table containing data related to the 240
detectors associated with the logic.
IDIGINP2 Table containing detectors configuration 240
data.
IDOUTPUT Table containing digital outputs 240
configuration data.
IEVENBUF The buffer where all events are stored. 5000
IFEDBCK2 Table containing feedbacks 150
configuration data.
IINPSTAT Dynamic table containing the status of 240
all detectors.
ILOGISTA Dynamic table containing the status of 240
all logics.
INODESTA Dynamic table containing the status of 512
all nodes (TemaServers) that are
configured in the system.
IOUTSTAT Dynamic table containing the status of 240
all outputs.
IPERCOME Table containing commands data to be 255
sent to the peripheral devices.
IPEREVEN Table containing events data to be sent to 512
the peripheral devices.
IPERSTAT Table containing statuses data to be sent 255
to the peripheral devices.
53
Table 1 Database format for Intrusion Detection Module (continued)
Table Description Number of Notes

records
ISCHEDCO Table containing scheduled commands 64
configuration data.
ITABZON2 Table containing zones configuration 128
data.
IZONESTA Dynamic table containing the status of 128
all zones.
RTUS DISPLAY
RTUs display
The RTU components are the base modules (readers, displays, keyboards) that
make up the miniterminals and the peripheral devices for the intrusion detection
module.
You can use this display to select the modules that are to be configured and to set
their operating modes. To do so, information requested from the peripheral level
will also be used.
Note that RTU A10/A11 components, that is, I/O modules, can be used to manage
field points and output devices, and as anti-intrusion devices (for example,
volumetric sensors).

Open the RTUs display page 55
Configure an RTU for intrusion detection page 56
RTU types managed by the intrusion detection module page 57
Tip
Hardware Configuration > RTUs display.
Guide > Configuration Displays Reference > Hardware Configuration > RTUs
display.
Open the RTUs display

Detection > Hardware Configuration > RTU.
Configuration > RTUs.
55
Configure an RTU for intrusion detection

In the RTU configuration display you can set up the RTU component to use for
intrusion detection.
1 Select Intrusion Configuration > Hardware Configuration > RTUs.

2 Enter the RTU ID and Description for the RTU component.
3 From the TemaServer drop-down list, select the intrusion-detection
TemaServer (TS ID01) that controls this RTU component.
4 From the RTU Type drop-down list, select the appropriate value. For a list of
the supported RTU types, see “RTU types managed by the intrusion detection
module” on page 57.
5 For instructions on setting the Neuron ID and Program ID refer to:
• Access Control Configuration Guide, section Configure a Temaline
System > Configure the RTU Components > Set the Neuron ID and
Program ID.
6 If applicable for the RTU component (only Bxx readers and K00 keyboard
modules), in the Configuration tab, from the Encoding Format drop-down
list select the appropriate credential type.
7 Complete the remaining fields as required. Refer to the above cited
documentation for details.
8 Click Save.
RTUS DISPLAY
RTU types managed by the intrusion detection module

The following table lists the RTU components managed by the intrusion detection
module, together with a description of each.
RTU type Description

RTU A10 4in - 4out (controlled inputs, O.C. outputs) DIN
module
RTU A11 ID I/O module 4 controlled inputs, 4 open collector
out (managed only from Tema ID and Tema SEC)
RTU B01 Magnetic card reader
RTU B03 Smart card contact reader (ISO 7816)
RTU B04 Proxy UNIQUE reader
RTU B07 Proximity HID reader
RTU B12 Smart card MIFARE contactless reader (ISO 14443)
RTU B19 Bi-directional proximity reader module for HID card
(based on Omnitek – Reader module MD15W)
RTU C02 Graphic LCD module (240x128 pixels)
RTU Q01 10W power supply (4 hour battery autonomy)
RTU Q03 60W power supply (4 hour battery autonomy)
RTU Q04 35W 24 h Battery management module (70W 12h)
RTU K00 Combo: reader based on keyboard
57
Miniterminals display
The miniterminals are the peripheral devices that make up the Man-Machine
Interface for the Intrusion Detection Module. The table below lists the four types
of miniterminals.
Operators who are enabled may use the miniterminals to manage the plant and to
perform specific operations on controlled objects. (For further information on
how to use the miniterminals, see “MT Display - User Manual”.)
You can use this display to configure the miniterminals and to specify the relevant
RTU components. When you are configuring a miniterminal, note that the
selection combo box and all selection lists display only those elements that are in
accordance with the operator’s enterprise model.

Miniterminal types and composition page 58
Open the Miniterminals display page 59
Miniterminals - Main tab page 59
Miniterminals - Activation tabs page 61
Miniterminals - Supervision tab page 62
Miniterminals - Alarm Settings tab page 62
Miniterminal types and composition
Miniterminal Composition and Description

Composition—RTU CO2 – Graphical Display
Description—Allows you to monitor and perform operations
on the plant, such as manually arming a zone, managing
alarms, executing specific commands on controlled objects,
configuring and modifying the operators’ validity, and so
forth.
MT Display
MINITERMINALS DISPLAY
Miniterminal Composition and Description

Composition—RTU CO2 with RTU BOx – Reader Module
(several read technologies)
Description—The functions are analogous to those of MT
Display, with the sole difference that the operator may access
it using his/her own card.
MT Display-MT Reader
Composition—RTU K00 – Reader based on keyboard
module
Description—Peripheral activation device protected by a
secret operator password. Allows you to execute the
feedbacks associated with this, and it may be used for
MT Keyboard arming/disarming a plant or zones, or for executing
commands on devices.
Composition—RTU BOx – Reader module using several
read technologies
Description—Peripheral device for general use that reads
the operator’s card code and allows the executing of the
MT Reader feedbacks associated with it; it may be used for arming/
disarming a plant or zones.
Open the Miniterminals display

Detection > Hardware Configuration > Miniterminals.
Configuration > Miniterminals.
Miniterminals - Main tab
Field Description
Identification
Acronym A unique acronym that identifies the miniterminal
within the system. The acronym can be made up of a
maximum of 8 alphanumerical characters (letters
from A to Z, or numbers from 0 to 9).
field.
59
Field Description
Point name The identifier of the point used in the EBI
environment. It is automatically filled with the same
value as the Acronym. If required, it is possible to
change it. It can contain up to 40 characters and it
must be unique.
Description A description of the miniterminal (up to 132
characters). Only 32 characters are sent to the
peripheral level.
Type The type of miniterminal to be configured. You have 4
options:
• MT Display—Graphical Display
• MT Keybpad —Reader based on keyboard
module
• MT Reader—Reader module
• MT Display-MT Reader—Display with a reader
module
Once you have selected a miniterminal type, the
display shows the tab(s) (depending on which
miniterminal type you have selected) that allow you to
configure both its composition and behavior.
Plant The drop-down list contains the plants that are already
configured. The miniterminal must be associated with
a plant. For further information, see “Plants display”
on page 20.
Configuration
This area allows you to select the RTU component(s) that make up the miniterminal
Image An icon that represents the type of RTU component.
RTU The drop-down list lets you select one of the RTU
components configured in the system
Description These fields are automatically filled in, in accordance
RTU Type with the RTU selected.
Location
Sites
MINITERMINALS DISPLAY
Miniterminals - Activation tabs

These tabs allow you to configure the actions, such as feedbacks or zone arming/
disarming, that can be executed from the miniterminal. The activation tabs that
appear depend on the selected type of miniterminal.
Field Description
Activation 1 tab
This tab appears for MT Keypad or MT Reader type miniterminals only. It allows you
to configure activations triggered by:
• A valid card transaction (in the case of MT Reader)
• Entry of a valid activation code + password (in the case of MT Keypad).
The activation code is required only if more than one activation was set for the
miniterminal).
Note: You can configure either a feedback activation or a zone arming/disarming
activation, but not both.
Activation Feedback 1 Use these fields to configure a feedback activation.
Activation Feedback 2 Each time there is a valid activation trigger (card
reading for MT Reader, or password/code entry for
MT Keypad) the miniterminal will toggle between
executing the feedbacks 1 and 2 configured here.
For example you can use these feedbacks to switch a
device on and off, or to activate its LEDs.
Zone associated Use this field to configure a zone arming/disarming
activation.
Each time there is a valid activation trigger (card
reading or password/code entry) the miniterminal will
toggle the status of this zone (if it is armed, it will be
disarmed, and vice versa), also based on the
management type and the time scheduling that have
been set for the zone
Denied feedback The feedback that is executed by the miniterminal if
the activation is denied, due to:
• Invalid card transaction, for MT Reader.
• Invalid code or password, for MT Keypad.
Activation 2-8 tab

This tab appears only for MT Keypad type miniterminals. It allows you to configure the
miniterminal so that, if operators enter both the proper activation code (a number from 2
to 8) and a valid password, they may execute 7 more activations.
Note: For each number, you can configure either a feedback activation or a zone arming/
disarming activation, but not both.
61
Field Description
Activations 2 - 8 The feedback that is executed when the operator types
both the corresponding activation code and a valid
password. The number (2 to 8) is the activation code
to be typed.
Zones 2-8 The zone that will be armed/disarmed depending on
its current status (e.g., if it is armed, it will be
disarmed), and based on the management type and the
time scheduling that have been set for the zone. The
number (2 to 8) is the activation code to be typed.
• For a detailed description of the activation procedures, the behavior of the

miniterminal and the system, as well as for a troubleshooting section, see the
MT Display User Manual that is provided with the Intrusion Detection
module, chapter “Working with the Miniterminals,” sections “MT Reader”
and “MT Keyboard.”
Miniterminals - Supervision tab

The Supervision tab associates the Miniterminal with displays and signatures. For
details about these fields, refer to:
Miniterminals - Alarm Settings tab

Minterminal, and their priorities. For details about these fields, refer to:
DETECTORS DISPLAY
Detectors display
The detectors, or the intrusion detection field points, allow the subsystem to
acquire the digital values measured by the field devices. They are controlled by
RTU A10/A11 components which communicate status changes of the detector to
the TemaServer ID responsible for managing associated actions.
The connection is effected by means of balanced inputs, so that, besides the
normal status and the alarm, the system is capable of detecting short circuits, cuts,
and tamper events.
The detectors may be associated with a zone and/or a logic, and in such a case,
they will inherit the corresponding status thereof (armed/disarmed).
For further information on how to manage detectors via the peripheral interface,
see MT Display – User Manual, section Introduction > Detectors.
For information about Go to:

Open the Detectors display page 63
Detectors - Main tab page 64
Detectors - Detector Type tab page 65
Detectors - Behavior tab page 68
Detectors - Feedback tab page 69
Detectors - Supervision tab page 70
Detectors - Alarm Settings tab page 70
Save data for multiple detectors page 71
Open the Detectors display

Detection > Hardware Configuration > Detectors.
Configuration > Detectors.
Note:
When configuring a detector, the selection combo box and all selection lists
display only those records that are in accordance with the operator’s enterprise
model.
63
Detectors - Main tab
Field Description
Identification
Acronym The acronym that identifies the detector within the
system. The acronym can be made up of a maximum
of 8 alphanumerical characters (letters from A to Z, or
numbers from 0 to 9).
field.
unique.
Plant The plant to which the detector belongs.
Physical Configuration
RTU The identifier of the RTU component to which the
detector is linked and which determines how it is
obtained. The drop-down list contains the RTU A10/
A11 components (intrusion type I/O modules)
belonging to the TemaServer ID that manages the
selected plant.
Detector Address The address of the detector within the RTU
component.
Normality Value The normality value that determines whether the
status of the detector is active or inactive. The
physical status of the detector is as follows:
• 0—contact closed (default)
• 1—contact open
If the normality value is 0 and the detector has a value
of 1 (contact open), the device is active. If the
normality value is 1 and the detector has a value of 0
(contact closed), the device is inactive.
Location
Sites
DETECTORS DISPLAY
Field Description
Detectors - Detector Type tab
Field Description
Detector Type From the drop-down list, you can select one of the
detector types that are supported by the intrusion
detection module.
The Check Time and Activation Time fields are
automatically filled with the default values for the
selected detector, but you can enter a different value.
For more information see “Description of detector
types” on page 66.
Check Time The delay utilized by the detector to manage the
emitting of alarms (expressed in seconds). You may
specify a value between 1 and 3600.
Activation Time Sets the delay utilized by an Alarm After Reset
detector type to manage the emitting of alarms
(expressed in seconds). You may specify a value
between 1 and 3600.
Test fields
The test feature involves activating the Test Output associated with the detector, verifying
the alarm condition, deactivating the output, and then verifying the normal condition for
the detector.
(Not available for Key or Reset Key detector types)
Enable Test Enables/disables the test feature for the detector,
meaning the capability of performing the active test
described above.
Test output If Enable Test is selected, this drop-down list

contains all Test type outputs configured for the plant.
From here, you can select the output to use for
performing the active test on the detector.
For digital output configuration see “Intrusion Digital
Output display” on page 72.
65
Field Description
Reset fields
The reset feature allows the detector to be returned to its normal status utilizing the
associated Reset Output. The reset can occur when the Acknowledge command is
executed (it can either be received by the Supervision Center, or performed manually at
the peripheral level)
(Not available for Key detector types)
Enable Reset Enables/disables the Reset feature for the detector,
meaning the capability of returning the detector to its
normal status utilizing the associated Reset Output.
Reset Output If Enable Reset is selected, this drop-down list
contains all Reset type outputs configured for the
plant. From here, you can select the output to be used
for performing a reset of the detector.
For digital output configuration see “Intrusion Digital
Output display” on page 72.
Typology assignment
All objects have a default typology, which determines the statuses, events, and commands
that are possible for that object. The typology may also be customized for the case of
detectors and logics. See “Typologies Configuration display” on page 78.
Typology Sets the typology for this detector.
The default value for detectors is IDINPUT, but the
drop-down list will also contain any available custom
configurations.
Description of detector types
Detector Type and Description Check Activation

Time Time
(default) (default)
Detector Not used Not used
Follows normal behavior. This is the default detector type.
Key Not used Not used
Detector that arms/disarms an element. This is never disarmed.
Alarm After Reset 30 sec. 30 sec.
Detector that does not generate an alarm on the first status
change, rather:
• It is reset for the time interval equivalent to the Check Time
that has been set;
• If the detector is still active after the Activation Time set has
passed, this generates an alarm.
DETECTORS DISPLAY
Detector Type and Description Check Activation

Time Time
(default) (default)
With delayed alarm 60 sec. Not used
Detector that, if it is armed and it detects an alarm condition,
behaves as follows:
• It waits for the Check Time that has been set;
• It verifies its own status, then, if it is still in the armed status,
it generates an alarm or if it is disarmed, it does not generate
an alarm (with the exception of the detectors with Alternate
Behavior).
With Pre-Alarm 30 sec. Not used
Detector that generates a pre-alarm on the first status change,
then:
• It waits for acknowledgment of the pre-alarm during the
Check Time that has been set;
• If the pre-alarm is acknowledged, it blocks the emission of
the alarm, it generates a pre-alarm return event, and it
launches the related feedback (if any). The detector remains
in the status of pre-alarm until status is reset to normal;
• If the pre-alarm is not acknowledged within the Check Time
it generates an alarm. At the end, the detector returns to the
normal status, and the pre-alarm return event and the alarm
return event are generated.
Reset Key 300 sec. Not used
Detector for checking and managing an alarm situation for the
plant. There are two possible scenarios for the detector’s
behavior:
• If there are no pending alarms and the detector is activated,
an activation event is emitted;
• If there are pending alarms, the emission of other alarms is
suspended for the duration of the Check Time that has been
set;
• If the detector is deactivated within the Check Time, all the
pending alarms are automatically acknowledged;
• If the detector is not deactivated within the Check Time an
activation event is emitted.
Upon completion of these operations, the plant is reset to normal
status.
67
Detectors - Behavior tab
Field Description
Zone The drop-down list allows you to associate with the
current detector one of the intrusion zones configured
for the plant. The arming/disarming of this zone
determines the arming/disarming of the detectors that
are associated with it.
Logic (1 to 4) Read-only fields that indicate which logic(s) are
associated with this detector. (See “Logics display” on
page 36.). A detector may be associated with 4 logics
simultaneously. If the detector is associated with a
logic, it does not send alarm signals directly, rather it
refers the signal to the pertinent logic.
Alternate Behavior Allows you to specify for the detector the use of an
alternate behavior (provided that the detector has been
associated with a zone); this allows the detector to
emit alarms, even when it is disarmed (useful, for
example, for an anti-theft button in a bank branch).
A detector with alternate behavior, in fact, can
manage two different types of alarms, according to its
current status (armed/disarmed):
• if the detector is armed, it takes on the status of
Active/Deactivated, generates the pertinent alarm
and performs the related feedback, if any. The
alarm indicates that the detector has been activated
while in the armed status;
• if the detector is disarmed, it takes on the status of
Alarm/Normal, generates the pertinent alarm and
performs the related feedback, if any.
Alarm Repetition Allows you to set the management of the alarm
repetition for bi-stable alarms based on their
acknowledgment.
The behavior is as follows:
• A detector sends an alarm and then returns to a
normal status: an alarm in entered in the alarm list
which needs to be acknowledged;
• The same detector goes into alarm more times
before the alarm is acknowledged: in these
occasions, no new alarm is generated, because this
already appears in the alarms list;
• Once the alarm is acknowledged, the original
situation is reset.
DETECTORS DISPLAY
Field Description
Auto disable Allows you to set the automatic disabling of the
detector if it is still changing from the alarm status to
the normal status, based on the time interval and the
number of repetitions that have been set.
Auto disable time period This text box is only enabled if the Auto disable
option has been selected.
Specifies the time period, in seconds, for the detector
to auto disable.
Auto disable number of repetition This text box is enabled only if the Auto disable
option has been selected.
Specifies the number of repetitions that must occur
within the time period defined before the detector is
disabled.
For example, if
• Auto disable is selected;
• Auto Disable Time Period is set to 120; and
• Auto Disable Number of Repetitions is set to 5,
the result is that if a given detector goes into alarm 5
or more times within a period of 2 minutes, the
detector is disabled. The detector then must be re-
enabled using a manual command (via the
miniterminal or the supervision center).
Operative Note The drop-down list allows you to associate an
operative note to the current detector. Operative notes
are string messages containing information that the
operator can see at the miniterminal display when
managing the plant. See “Operative Notes display” on
page 41.
Detectors - Feedback tab

You can use this tab to set the feedbacks to execute in the event of the detector
alarm conditions listed below.
Field Description
Short-circuit Alarm Feedback The feedback executed if the RTU component detects
a short circuit of the detector.
Short-circuit Alarm Feedback The feedback executed if the RTU component detects
Reset a reset of the short circuit of the detector.
Cut Alarm Feedback The feedback executed if the RTU component detects
a cut status in the detector cabling.
69
Field Description
Cut Alarm Feedback Reset The feedback executed if the RTU component detects
a reset of the cut status in the detector cabling.
Pre-Alarm Feedback The feedback executed if the RTU component detects
a pre-alarm status for the detector.
Return Pre-Alarm Feedback The feedback executed if the RTU component detects
a return of the pre-alarm status.
Alarm Feedback The feedback executed if the RTU component detects
a logic alarm of the detector.
Return Feedback The feedback executed if the RTU component detects
a reset of the detector alarm status.
Tamper Feedback The feedback executed if the RTU component detects
a tamper alarm of the detector.
Tamper Return Feedback The feedback executed if the RTU component detects
a reset of the detector tamper alarm.
Feedback on Start Test The feedback performed upon startup of the detector
test.
Feedback on End Test The feedback performed upon completion of the
detector test.
Activate Feedback The feedback executed when the RTU component
detects that the detector has been activated while in
armed status. It only applies to detectors with
Alternate Behavior.
Deactivate Feedback The feedback executed when the RTU component
detects the de-activation of the detector. It only
applies to detectors with Alternate Behavior.
Detectors - Supervision tab

The Supervision tab associates the Detector with displays and signatures. For
details about these fields, refer to:
Detectors - Alarm Settings tab

Detector, and their priorities. For details about these fields, refer to:
DETECTORS DISPLAY
Save data for several detectors

The Save all elements button allows you to apply a change in bulk, to multiple
detectors at the same time. To do this:
1 If required, apply a filter so that the selection list at the top includes only the
detectors to which you want to apply the change.
2 Select the detector you want to use as a template, and make any required
changes to its fields.
3 Click Save all elements.
4 In the Save all elements dialog box, select the check boxes for the fields
whose configuration you want to copy to all the other detectors. For example,
the Normality Value of this detector.
5 Click Save selected. The selected fields are copied to all the detectors
currently in the drop-down list at the top.
For more information refer to:
reference > Common Operations > Configure elements > Modify multiple
elements at the same time.
71
Intrusion Digital Output display

Intrusion digital outputs allow you to execute specific commands; they can be
activated either from the Supervision Center, using the miniterminal, or via a
feedback (based on a specific event or in scheduled mode).
In particular, the Intrusion Detection Module of Temaline Interface manages the
following digital outputs:
Outputs connected to an RTU A10 or A11 (I/O type RTU) component.

Specifically, the outputs in the ID Module manage the testing and reset of
detectors, in addition to the normal actuations (such as sirens, telephone dialers,
and so forth). Using this display you can configure the outputs that are connected
to the RTU A10, if they are either within the ID Panel, or connected to the
Lonworks.
General Relays connected directly to the ID Panel

These are the alarm general relay and the failure general relay. These outputs have
a preset behavior and do not need to be configured; they emit an alarm signal if
the ID Panel is switched off or in failure.
Generally, the outputs can be associated with a zone, and in this case, they follow
the status of that zone (armed/disarmed).
For information about Go to:

Open the Intrusion Digital Output display page 72
Intrusion Digital Output - Main tab page 73
Intrusion Digital Output - Supervision tab page 75
Intrusion Digital Output - Alarm Settings tab page 75
Open the Intrusion Digital Output display

Detection > Hardware Configuration > Intrusion Digital Output.
Configuration > Intrusion Digital Output.
Note: When configuring an output device, the selection combo box and all
INTRUSION DIGITAL OUTPUT DISPLAY
Intrusion Digital Output - Main tab
Field Description
Acronym An acronym that identifies the digital output within
the system. The acronym can be made up of a
maximum of 8 alphanumerical characters (letters
from A to Z, or numbers from 0 to 9.)
field.
Point ID The identifier of the point used in the EBI
modify it (up to 40 characters).
Plant The plant to which the output belongs. (See “Plants
display” on page 20.)
RTU ID An acronym that identifies the RTU component to
which the output device is linked. The drop-down list
contains the RTU A10/A11 components (intrusion
type I/O modules) belonging to the TemaServer ID
that manages the selected plant.
Output Address The address of the output device within the RTU
device (1 to 4).
Output Type The drop-down list allows you to set the type of
output to be configured:
• General Purpose Output—Configure a device
for general purpose activations (default value).
• Test Output—Configure a device to manage the
test on detectors.
• Reset Output—Configure a device to manage the
reset of detectors after the alarm acknowledgment.
For information about the Test and Reset features, see
the Test fields and Reset fields in the table “Detectors
- Detector Type tab” on page 65”)
73
Field Description
Normality Value The normality value that determines whether the
status of the output device is active or inactive. The
physical status of the output device is as follows:
• 0—contact closed
• 1—contact open
If the normality value is 0 and the output device has a
value of 1 (contact open), the device is active. If the
normality value is 1 and the output device has a value
of 0 (contact closed), the device is inactive.
Starting Value The value assigned to the output at system startup. If
the starting value is 1 and the normality value is 0, the
output will be active when the system starts up.
Length of Operation The length of time for which the output device is set
to a given value (expressed in seconds). If this value is
0, execution is bi-stable, i.e. the output device will
remain active until a specific command places it in
inactive status.
Operation Type A combo box containing two options:
• Fixed
• Intermittent
The former option generates a fixed response; for
example, if a light is turned on for a certain period of
time. Alternatively, an intermittent response
corresponds to a flashing light.
Associated Zone The drop-down list allows you to associate to the
output one of the zones configured for the plant. The
arming/disarming of this zone determines the arming/
disarming of the digital outputs that are associated
with it.
If desired, you can double-click to view the Intrusion
Zones display display, which allows you to configure
them.
Restorable It allows you to enable/disable the capability of being
restorable for the output, that is the capability of
blocking the relevant actuation following a specific
plant command. This option is available only if the
output type currently selected is General Purpose
Output.
Output restore on communication It allows to specify if the Starting Value of the output
failure must be automatically restored when communication
between the RTU and the TemaServer ID is
interrupted.
Sites
INTRUSION DIGITAL OUTPUT DISPLAY
Field Description
Intrusion Digital Output - Supervision tab

The Supervision tab associates the Intrusion Digital Output with displays and
signatures. For details about these fields, refer to:
Intrusion Digital Output - Alarm Settings tab

Intrusion Digital Output, and their priorities. For details about these fields, refer
to:
75
Administration
5
The Administration group comprises displays for configuring various functions
relating to rights, storage and utilities. Some of these displays are specific to the
intrusion detection module, while others are in common with access control.

Utility tools
Summary Point Creation display Temaline Access Control Configuration Guide,
section Configuration displays reference >
Administration displays > Summary Point
Creation display.
Typologies Configuration display page 78
Storage
Historical Data Storage display Temaline Access Control Configuration Guide,
Administration displays > Historical Data
Storage display.
Rights and Visibility
Sites display Temaline Access Control Configuration Guide,
Administration displays > Sites display
Stations display Temaline Access Control Configuration Guide,
Administration displays > Stations display
Peripheral Operators display page 85
Peripheral Profiles display page 83
77
5 – ADMINISTRATION
Typologies Configuration display

Each controlled object (TemaServers, miniterminals, zones, logics, detectors, and
so forth) has its own default typology in terms of the statuses that it may assume,
the events (alarm conditions) that it may generate, and the commands that can be
run on it.
For further information, refer to “Statuses, Commands, and Events” on page 109.
For the case of detectors and logics, in addition to the default typologies, you can
create customized typologies, which are to be associated with the individual
objects during their configuration.
You cannot create customized typologies for the other types of objects.
This feature, therefore, allows you to adapt the behavior of the detectors and the
logics to the given type of plant (see “Detectors display” on page 63 and “Logics
display” on page 36).

Open the Typologies Configuration display page 78
Typologies Configuration - Main tab page 78
Typologies Configuration - Status tab page 79
Typologies Configuration - Alarm tab page 79
Typologies Configuration - Command tab page 80
Create a custom typology page 81
Open the Typologies Configuration display

Detection > Administration > Typologies Configuration.
• From the Intrusion Configuration navigation pane: Select Utility Tools >
Typologies Configuration.
Typologies Configuration - Main tab
Field Description
Identification
TYPOLOGIES CONFIGURATION DISPLAY
Field Description
Acronym The unique identifier for the typology. The acronym
can be made up of a maximum of 8 alphanumerical
characters (letters from A to Z, or numbers from 0 to
9.) If a Brief name has been assigned to the typology,
the acronym starts (first 4 characters) with the Brief
name.
field.
Description A description of the typology (up to 132 characters).
Only 32 characters are sent to the peripheral level.
Brief The brief name of the typology (max. 4 characters). It
is used for the duplication of the typology.
Typologies Configuration - Status tab

This tab enables you to customize the statuses that objects belonging to this
typology may assume.
Field Description
EBI area
This column shows the statuses as they appear on the Supervision Center side.
Default string The string that describes this status in the Point Detail
Display
New string Here you can enter a different string to change the
default one
TemaServer area
This column shows the statuses as they appear on the Miniterminal--that is controlled by
the TemaServer.
Default string The string that describes this status on the
Miniterminal.
default one.
Typologies Configuration - Alarm tab

This tab enables you to customize the alarm conditions that objects of this
typology may generate, and how those alarms are managed.
79
Field Description
EBI column
Configures how the alarm is managed by the Supervision Center.
Default string The string that describes this alarm on the Supervision
Center side.
default one.
Enable Select the check box alongside those items that you
want to be treated as alarms. These will be included in
the event list and in the alarm summary
Priority For each enabled item, you can set the desired alarm
priority from the drop-down list:
• For Low, High, or Urgent, the system displays the
event in the alarm summary, with order of
precedence urgent > high > low, and allows
operators to manage it. The event is also stored in
the event file.
• For Journal, the system stores the event in the
event file, but does not display it in the alarm
summary.
Subpriority Here you can enter a value between 1 and 15, that
determines the precedence for alarms having the same
Priority
TemaServer column
Configures how the alarm is managed at the miniterminal level.
Log The event is stored in the event file.
Alarm The event is displayed in the alarm summary.
Print
Sound Sets whether an audible alarm is issued, and its
duration. Options are:
Always, Short, or Never.
Typologies Configuration - Command tab

This tab enables you to customize the commands for objects of this typology.
Field Description
Default string The string currently used to describe this command.
TYPOLOGIES CONFIGURATION DISPLAY
Field Description
default one.
Create a custom typology

For intrusion detectors and logics, you can create customized typologies which
may be assigned to objects in place of the default ones.
1 Select Intrusion Configuration > Utility Tools > Typologies
Configuration.
2 From the drop-down list at the top, select the default typology that you want to
use as the basis for the new custom typology (Intrusion Detectors or Logic).
3 Click Duplicate to make a copy of the selected typology.
4 Enter an Acronym and Description for this custom typology.
5 In the Status tab, you can customize the descriptions of the statuses for
objects of this typology. Each status occupies a separate row:
• In the EBI area, the Default String shows the status as displayed on the
Supervision Center side. This string describes the status of the object in
the Point Detail Display.
• In the TemaServer area, the Default String column shows the status as it
is displayed on the Miniterminal--that is controlled by the TemaServer.
You can customized these strings by typing the desired string into the New
String column.
6 The Alarms tab shows all the alarm conditions that objects of this typology
may generate, along with their management modes:
• In the EBI area, Default String column, all of the alarm conditions are
displayed from the Supervision Center side, along with the modes for
handing them, in terms of enabling and priority.
• In the TemaServer area, the management modes for the alarms conditions
at the miniterminal level are displayed:
Log—if this option is selected, the event is sent to the events file.
Alarm—if this option is selected, the event is sent to the alarm list.
Print—Not used. It will be implemented soon.
Sound—this field allows you to manage the acoustical alarm emission;
the possible options are Always, Short, Never.
7 Make the changes desired to the current settings, then click the Commands
tab. This tab shows all the commands that can be performed on the objects,
based on the default settings.
81
8 Type any new commands into the New String column.

9 Upon completing the operations, click Save.
10 The typology thus configured may be associated with the individual objects in
the Typology field on the configuration displays for Detectors and Logics.
PERIPHERAL PROFILES
Peripheral profiles
This feature enables you to define the rights of operators who are enabled to
manage the plant from the Intrusion Detection module miniterminals, that is, via
peripheral devices.
In particular, the peripheral profiles define the access rights to the management
features that are available from the miniterminals. Each operator may be assigned
a different profile, and, consequently, different rights in relation to these features.
The operator profile is specified at the time of accessing the miniterminal. (For
further information, see MT Display – User Manual, chapter “Introduction”,
section “Operators”).
The Temaline Interface Intrusion Detection module is provided with four default
profiles, to which different rights to the features are associated:
• Manager
• Operators
• Service
• Supervisor
In particular, the Service profiles allow you to access the maintenance and
general testing functions of the ID plant using the MT Display miniterminal
which provides the peripheral interface for the Module.
You may create new profiles, or you may use the default profiles for creating
customized profiles.

Open the Peripheral Profiles display page 83
Peripheral Profiles - Main tab page 84
Create a custom peripheral profile from a default one page 84
Open the Peripheral Profiles display

Detection > Administration > Peripheral Profiles.
• From the Intrusion Configuration navigation pane: Select Rights and
Visibility > Peripheral Profiles.
Note: When configuring a peripheral profile, the selection combo box and all
83
Peripheral Profiles - Main tab
Field Description
Acronym The unique identifier on the system of the peripheral
profile.
Description A description of the peripheral profile.
Function tree The tree lists the functions available from the
miniterminal.
• Functions are shown grouped. Click the + sign to
expand a grouping (for example Zones) and show
its secondary functions (for example Zones list,
Zone commands, etc.)
• The check box alongside each function indicates
its current status (enabled or disabled). To enable
or disable a function, select or deselect the check
boxes as needed.
Facility
Create a new peripheral profile starting from a default one

1 Select Intrusion Configuration > Utility Tools > Peripheral Profiles.
2 From the drop-down list at the top, select the profile (Manager, Operator,
Service or Supervisor) that you want to use as the basis for the new profile.
3 Click Duplicate.
4 Enter an Acronym and Description for the new profile.
5 In the function tree, enable/disable the functions as required for the new
profile.
6 Click Save.
PERIPHERAL OPERATORS
Peripheral operators
Peripheral operators are those who have access to the plant management
functions via the Man-Machine Interface of the Intrusion Detection module, that
is, the miniterminals (see section “Miniterminals display” on page 58 in this
manual and the manual for use of peripheral devices, MT Display - User Manual).
Using miniterminals, operators can manage the plant in terms of:
• managing the login passwords and validity dates for operators
• displaying controlled objects and performing commands upon these (zones,
logics, detectors, plants)
• feedbacks execution
• acknowledging and managing alarms
• maintenance and general testing of the ID plant.
The access rights for these features depend upon the profile associated with the
operator. For further information, see “Peripheral profiles” on page 83.

Open the Peripheral Operators display page 85
Peripheral Operators - Main tab page 85
Open the Peripheral Operators display

Detection > Administration > Peripheral Operators.
• From the Intrusion Configuration navigation pane: Select Rights and
Visibility > Peripheral Operators.
Note: When configuring a peripheral operator, the selection combo box and all
Peripheral Operators - Main tab
Field Description
Identification
Operator The unique identifier for the operator on the system.
Description A description of the operator.
85
Field Description
Plant The plant(s) for which the operator is enabled. All of
the plants that are configured will be displayed in the
pane. A check mark indicates the selection.
Profile You can select one of the default peripheral profiles
from the drop-down list, or one of the profiles
configured using the Peripheral Profiles display. The
operator will then have the access rights to the plant
management features defined in the selected profile.
Password
Starting Password The password to be attributed to the operator, which
allows him/her to access the plant management
features via the MT Display or MT Keyboard
miniterminals. (For further information, see the MT
Display – User Manual which is provided the
Intrusion Detection module.)
After you enter the password, the Confirm text box
appears. You must type the password here a second
time.
Status The password status. There are two possible options:
Enabled and Disabled.
Start Date The beginning date of the period of validity of the
password.
End Date The ending date of the period of validity of the
password.
The validity dates for the password assigned to the
operator may be modified using the MT Display
miniterminal, provided that the operator profile is
configured for this feature. (For further information,
see MT Display – User Manual, chapter “MT
Display”, section “Operators List > Operator Data
Change”.)
Reset password button If necessary, you may reset the operator’s password to
the one given during configuration, for cases where it
was later modified. The Reset Password button
enables you to re-establish the Start Password as the
current password for the operator
Code
Card Code The code for plant management via the MT Reader
miniterminal, made up of a maximum of 20
alphanumerical characters.
Edition The edition of the card. Applies only to reader
modules.
Facility
PERIPHERAL OPERATORS
Field Description
87
Point detail displays - ID
6
This chapter describes the point detail displays specific to the intrusion detection
module.
Heading See
Using Point Detail displays page 90
Point Detail display - TemaServer page 91
Point Detail display - Plant page 96
Point Detail display - Miniterminal page 98
Point Detail display - Detector page 100
Point Detail display - Output Device page 102
Point Detail display - Zone page 104
Point Detail display - Logic page 106
For information about other point detail displays (e.g RTUs, Feedbacks,
Summary Points) which are shared between ID and Temaline interface, refer to:
• Temaline Access Control Configuration Guide, section Point detail display

operations.
89
6 – POINT DETAIL DISPLAYS - ID
Using point detail displays

Point detail displays allow you to check the real-time status of dynamic objects
They also allow you to interact with these objects, for example running
commands or configuring parameters.
Layout of point detail displays

The face plate on the left-hand side of each display shows the main parameters,
such as the name of the device, its graphical representation and its current status.
• For information regarding the status of the various objects and their graphical
representation, see “Statuses, Commands, and Events” on page 109.
The right-hand side of the display contains tabs that allow you to view and
modify specific parameters associated with the device.
• The General tab contains detailed information about the current values of the
object and lets you run commands on the object. Specific check boxes,
buttons, and combo boxes allow you to run commands and modify the status
of the object.
• The Recent Events tab provides a list of the events generated by the object,
together with a description of each.
For further information refer to:
• Enterprise Buildings Integrators - Operators Guide.
operations > Overview of point detail displays.
Access a point detail display

You can access a point detail display in the following ways:
• Press F12, or click (Detail) in the EBI toolbar, enter the first few letters
of the Acronym (ID) in the field, then click OK.
• In the Command field of the EBI toolbar, enter the first few letters of the
Acronym (ID) and press F12.
For detailed instructions refer to:
operations > Overview of point detail displays > Access a point detail
display.
POINT DETAIL DISPLAY - TEMASERVER
Point Detail display - TemaServer
TemaServer PDD - General tab
Field Description
Identification
Acronym The acronym which identifies the TemaServer.
IP Address The network address of the TemaServer.
Group The group to which the TemaServer belongs.
Settings
Alarm relay disabled This command allows enabling/disabling the alarm
general relay that is connected to the Tema ID Panel.
Tamper relay disabled This command allows enabling/disabling the tamper
relay that is connected to the Tema ID Panel.
Failure relay disabled This command allows enabling/disabling the failure
general relay that is connected to the Tema ID Panel.
Displays
These fields are read-only here. They are set in the configuration display for the object,
under the Supervision tab.
Associated display The name of the page associated with this object.
91
Field Description
Alarm instructions display The name of the display with the instructions for
managing the alarms associated with the object in
question.
Buttons
The buttons on the right-hand side of the display, which allow you to run specific
commands, are described below.
Send date/time Forces the time and date on the TemaServer.
Reset CTU
Reset database Deletes the contents of the database on the
TemaServer and prepares it for a new download
request.
Information request This field allows you to enter information regarding
the TemaServer configuration in the supervision
center database.
Status request This field allows you to establish the current status of
the object, i.e. the status as displayed in the face plate.
Configuration request This field allows you to send a request to the
TemaServer for a list of configured RTU components,
together with the Neuron ID and the Program ID of
each. For further information, see “Configure an RTU
for intrusion detection” on page 56.
Binding request This field allows you to request execution of the
binding procedure.
Enable Telnet connection Enables the Telnet connection to the TemaServer.
Disable Telnet connection Disables the Telnet connection to the TemaServer.
EBI Dialup on Used to manually establish and terminate the dialup

EBI Dialup off connection from the Supervision Center to the
TemaServer.
Note: These two buttons are displayed only if the
TemaServer is configured to use a PPP remote
connection. (For details, see “Configure a TemaServer
for intrusion detection” on page 45).
Upload DB It allows launching the upload of a portion of the
database from the TemaServer ID to the Supervision
Center, provided that the TemaServer ID has been
properly set. For further information, see “Uploading
the TemaServer database” on page 94.
TemaServer PDD - Recent Events tab

This tab lets you view events associated with the object being controlled. For
details see:
operations > Overview of point detail displays > Recent Events tab.
TemaServer PDD - Firmware tab

Shows the firmware release currently installed on the TemaServer and on its
controlled RTU devices. Click + next to a grouping to expand the list of all items
in that group.
Field Description
Group by TemaServer Groups the displayed objects by the TemaServer that
controls them. (default)
Group by Type Groups the objects by type
Print Lets you print a report of the data shown in the point
detail display
93
Uploading the TemaServer database

This procedure allows uploading a portion of the database from the TemaServer
ID to the Supervision Center.
You can use it if the TemaServer ID has been configured locally, or using a local
interface, without being connected to the supervision center (an example can be a
new branch that has not yet physically connected to the company's headquarter).
To secure the building, once the connection is available, you have to update the
Supervision Center's database with the data that are stored in the TemaServer
memory.
To upload the TemaServer database:

1 Manually set the DB Upload Required for the TemaServer ID using Telnet.
To access a Telnet session, choose Start > Run > Telnet from the Windows
taskbar.
2 Type in the following command:
UDB WAIT_UP SET
In this way, the TemaServer ID is prepared for uploading his database to the
Supervision Center.
For further information on how to use a Telnet session and on the
configuration prerequisites for the TemaServer, see theTemaline Access
Control Configuration Guide chapter “Installing and Configuring the System,
” section “Configuring the TemaServer - Using the TEMA Virtual Monitor
for Setting the Parameters.”
3 Click the Upload DB button in the TemaServer ID detail display. The
uploading will start. If you did not set the “DB upload required” status for the
TemaServer, the Upload not allowed event will be generated.
Only a portion of the database will be uploaded, and in particular the
following tables:
Table name Data related to

AC_CTU_CFG TemaServer
ID_MT Miniterminals
AC_RTU_CFG RTU components
ID_PLANT Plant
ID_ZONE Intrusion zones
ID_LOGIC Logics
ID_DIGITAL_INPUT Detectors
ID_DIGITAL_OUTPUT Digital outputs
ID_OPERATIVE_NOTE Operative note
Table name Data related to

ID_FEEDBACK Feedbacks
95
Point Detail display - Plant
Plant PDD - General tab
Field Description
Identification
Acronym The acronym that identifies the plant
TemaServer The TemaServer ID that manages the plant.
Displays
question.
Buttons
Status Request This field allows you to establish the current status of
the object, i.e. the status as displayed in the face plate.
Test all Zones Runs the test on all zones of the plant and on all
detectors.
Overtime booking Books the overtime for all zones of the plant.
Armed Arms the plant and all zones that make it up after
running the test,
POINT DETAIL DISPLAY - PLANT
Field Description
Disarmed Disarms the plant for all zones that make it up.
Restore Interrupts all feedbacks in progress and restores all the
restorable type outputs of the plant.
Set to maintenance Sets the maintenance working mode for the plant
Set to Trying-out Sets the general testing mode for the plant.
Set to Operational Restore the operational working mode at the end of
the maintenance and general testing modes.
Alarm list Acknowledge Acknowledges the peripheral alarm list for the plant.
Alarm list deletion Deletes the peripheral alarm list for the plant.
Reset Plant Arm Status Restores the armed status for all zones of the plant.
Plant PDD - Recent Events tab

details see:
Plant PDD - Plant Zones tab

This tab allows you to select a zone of the plant and then change some of the
parameters that have been set for the zone, such as the schedule plan for arming/
disarming it. Press Save for implementing your settings.
For further information on the fields in the display and their function, see section
“Intrusion Zones display” on page 28.
97
Point Detail display - Miniterminal
Miniterminal PDD - General tab
Field Description
Identification
Acronym The acronym that identifies the miniterminal
Type The miniterminal type:
• MT Display
• MT Display-MT Reader
• MT Reader
• MT Keypad
Plant The intrusion detection plant to which the
miniterminal belongs.
Buttons
Status Request It allows you to send a request to the TemaServer for
information regarding the current status of the
Miniterminal, i.e. the status as displayed in the face
plate.
POINT DETAIL DISPLAY - MINITERMINAL
Field Description
Displays
question.
Miniterminal PDD - Recent Events tab

details see:
99
Point Detail display - Detector
Detector PDD - General tab
Field Description
Identification
Acronym
RTU The RTU component that manages the detector.
Zone The zone associated with the detector.
Detector Address The address of the detector within the RTU
component.
Detector Type The detector type:
• Detector
• Key
• Detector with test
• Detector with reset
• Detector with test and reset
Plant The plant to which the detector belongs.
Alarm Repetition If this check box is selected, the management of bi-
stable alarms repetition is enabled for the detector,
before they are acknowledged. (See “Detectors -
Behavior tab” on page 68).
POINT DETAIL DISPLAY - DETECTOR
Field Description
Settings
Disabled This is a command. To disable the detector, select the
check box. The detector will no longer generate
events.
Disarms This is a command. To disarm the detector, select the
check box. The detector will no longer generate
enable/disable events. It will only generate technical
events (such as cut and short circuit).
Buttons
Status Request This button allows you to send a request to the
TemaServer for information regarding the current
status of the detector, i.e. the status as displayed in the
face plate.
Test It allows performing the test on detector. Only applies
to detectors with test capability.
Reset It allows restoring the normal status for the detector.
Only applies to detectors with reset capability.
Displays
question.
Detector PDD - Recent Events tab

details see:
101
Point Detail display - Output Device
Output Device PDD - General tab
Field Description
Identification
RTU The RTU component responsible for controlling the
output device.
Zone The zone associated with the output device.
Settings
Disable This is a command. To disable the output device,
select the check box. The output device will no longer
generate events.
Disarm This is a command. To disarm the output device,
select the check box. It will not transmit enable/
disable events. It will only transmit events of a
technical nature (cut, short circuit).
Activate This is a command. To activate the output device,
select the check box.
Displays
POINT DETAIL DISPLAY - OUTPUT DEVICE
Field Description
question.
Buttons
Status Request This command button allows you to send a request to
the TemaServer for information regarding the current
status of the field point, i.e. the status as displayed in
the face plate.
Output Device PDD - Recent Events tab

details see:
103
Point Detail display - Zone
Zone PDD - General tab
Field Description
Identification
Zone management type Indicates the zone management type: Manual,
Automatic, Automatic with manual disarm,
Semiautomatic, Confirmable.
Plant The plant to which the zone belongs.
Settings
Disable This is a command. To disable the zone so that events
are no loner generated, select the check box.
Disarm This is a command. To disarm the zone, select the
check box. The detectors associated with this zone
will no longer generate enable/disable events and will
only generate technical alarms (cut and short circuit).
It will not be possible to execute commands on output
devices associated with the zone.
Buttons
status of the intrusion zone, i.e. the status as displayed
in the face plate.
POINT DETAIL DISPLAY - ZONE
Field Description
Test It allows launching the test on the zone
Overtime booking It allows booking the overtime for the zone
Reset Zone Alarm Stats Restores the armed status for the zone; the zone will
be re-armed based upon the schedule plant for arming/
disarming
Displays
question.
Zone PDD - Recent Events tab

details see:
105
Point Detail display - Logic
Logic PDD - General tab
Field Description
Identification
Zone The zone to which the logic is associated.
Plant The plant to which the logic belongs.
Settings
Disarm This is a command. Select the check box to disarm the
logic and all detectors associated with it.
Buttons
status of the logic, i.e. the status as displayed in the
face plate.
Displays
question.
POINT DETAIL DISPLAY - LOGIC
Logics PDD - Recent Events tab

details see:
107
Statuses, Commands, and
Events 7
This chapter provides the complete list of statuses, commands, and events
associated with all the objects managed by the Intrusion Detection module of the
Temaline Interface subsystem. This information is organized by object, as
follows:
Object Statuses Commands Events

TemaServer ID page 110 page 113 page 115
Plant page 117 page 118 page 118
Miniterminal page 120 page 120 page 121
Detector page 122 page 124 page 124
Output device page 126 page 127 page 127
Zone page 129 page 130 page 131
Logic page 132 page 133 page 133
Statuses and commands described in this chapter constitute the default typologies,
that is the ensemble of the statuses, commands and events for each object
controlled by the Intrusion Detection module. However, for detectors and logics,
you can create customized typologies that you might associate with individual
objects during their configuration, for their behavior to match your specific needs.
For further information, see “Typologies Configuration display” on page 78.
Objects whose typology is shared between the Intrusion Detection module and
the Temaline Interface subsystem (i.e., RTUs, Feedback, Summary Point, and
System) are not described within this section; for further information, see the
Temaline Access Control Configuration Guide that is provided with the
installation kit, chapter “Temaline Point Parameters.”
109
7 – STATUSES, COMMANDS, AND EVENTS
TemaServer
TemaServer statuses
Icon Status Value Description

NOT DETECTED 0 The Supervision Center does not have
information regarding the status of the
device. It is possible that the
communication management process is
not running.
Sky Blue
OUT OF ORDER 1 The TemaServer cannot communicate
with the communication center. The
failure refers both to the LAN and to the
dial-up connection. This status is set by
the Supervision Center.
Yellow
PANEL SWITCHED 2 The panel ID has been switched off
OFF because of the power failure on the
network and the battery failure.
Yellow
TAMPER ALARM 3 The TemaServer is open.
Red
LAN FAILURE 5 The Supervision Center cannot
communicate with the central unit using
the LAN. In case of dial-up, the
communication on the switched line
may be also interrupted. This status is
Yellow set by the Supervision Center.
RESET DB 6 Following a specific action, the
REQUIRED download to the TemaServer of the
database is required. This status is set
by the Supervision Center.
Yellow
TEMASERVER

DB UPLOAD 7 Database upload has been required.
REQUIRED This status is set by the Supervision
Center.
Blue
DOWNLOAD DB 8 Database download is in progress from
Sky Blue
DB UPLOAD IN 9 The database upload is in progress. This
PROGRESS operation allows the Supervision Center
to receive a TemaServer DB content.
Sky Blue
BINDING 10 Binding of RTU components in
UNDERWAY progress.
Purple
PRIMARY VOLTAGE 12 A power failure was detected on the
FAILURE network.
Red
NO ELECTRICAL 13 The electrical supply to the TemaServer
SUPPLY has been interrupted.
Yellow
RING CUT 14 A cut has been detected in the ring; it
only refers to RTUs in ring connection.
Red
111

RING SHORT 15 A short circuit has been detected in the
ring; it only refers to RTUs in ring
connection.
Red
FUSES GENERAL 16 Alarm on the power supply fuse of the
ALARM ID panel.
Yellow
BATTERY DEAD 17 The internal battery is dead.
Yellow
BATTERY LEVEL < 18 The level of the internal battery is
25% below 25%.
Yellow
BATTERY LEVEL < 19 The level of the internal battery is
10% below 10%.
Yellow
LAST DIALUP CALL 22 The dial-up call towards the
FAIL Supervision Center has failed. This
status is set by the Supervision Center.
Yellow
DIALUP IS 25 The modem dial-up connection between
WORKING the TemaServer and the Supervision
Center has been activated. This status is
set by the Supervision Center.
Green
TEMASERVER

DISABLE PANEL 4 The alarm relay on the ID panel is
ALARM RELAY disabled.
Red
TAMPER RELAY 27 The tamper on the ID panel is disabled.
DISABLED
Red
DISABLE PANEL 28 The failure relay on the ID panel is
FAILURE RELAY disabled.
Red
NORMAL 26 The TemaServer is functioning
normally.
Green
BAD POINT - Insignificant value. The chain of
applications/communication devices
used for status display has been
temporarily interrupted.
Gray
Commands on the TemaServer ID
Command Description EBI Parameter EBI Value

Status Request Determines the current status of the Commands 2
object.
Information Request Enters TemaServer configuration Commands 1
information in the database.
Peripheral Device Sends a request to the TemaServer for Commands 3
Configuration a list of its RTU components.
113
Command Description EBI Parameter EBI Value

Binding Request The TemaServer will perform the Commands 4
binding procedure for all RTUs.
Reset CTU Restarts the TemaServer without Commands 9
losing the database. You may run this
command via the detail display of the
TemaServer ID, other than by using
the miniterminal.
TemaServer Dialup Forces a dialup connection from the Commands 16
on TemaServer to the Supervision
Center.
TemaServer Dialup Disables manually the dialup Commands 17
off connection from the TemaServer to
Reset database Resets the peripheral database of the Commands 7
TemaServer.
Date/time sent Forces the time and date on the Commands 8
TemaServer.
Forced DB as invalid Forces the database invalidity. Commands 11
EBI Dialup on Manually activates a dial-up Commands 12
connection from the Supervision
Center to the TemaServer.
EBI Dialup off Manually disables the dialup Commands 13
connection from the Supervision
Center to the TemaServer.
Enable Telnet Enables the Telnet connection to the Commands 18
connection TemaServer.
Disable Telnet Disables the Telnet connection to the Commands 19
connection TemaServer.
Disable central Disables the tamper on the ID panel. DisableTampe 1
tamper r
Enable panel tamper Enables the tamper on the ID panel. DisbleTamper 0
Disable panel alarm Disables the alarm relay on the ID DisableAlarm 1
relay panel. Relay
Enable panel alarm Enables the alarm relay on the ID DisableAlarm 0
relay panel. Relay
Disable panel failure Disables the failure relay on the ID DisableFailure 1
relay panel. Relay
Enable panel failure Enables the failure relay on the ID DisableFailure 0
relay panel. Relay
TEMASERVER
Events generated by the TemaServer ID
Event Description
Drilling alarm An alarm has been detected on the drilling protection of
the central unit.
General fuse alarm Alarm on the power supply fuse.
Modem fuse alarm Alarm on the modem's power supply fuse.
Tamper alarm The TemaServer has detected an attempt to open the
device.
Battery dead Level of internal battery is approaching 0%.
Battery 1 failure The test on the battery 1 did not succeed.
Dialup fail The last attempt to establish a dial-up connection failed.
Binding error An error occurred during the binding procedure. Binding
was unsuccessful for some RTU components.
LAN failure Interruption of communication with the Supervision
Center.
Primary voltage failure The Supervision Center cannot communicate with the
center using the LAN. In case of dial-up, the
communication on the switched line may also be
interrupted.
Table name error Inconsistency caused by the database alignment
procedure on the TemaServer.
Block sequence error Inconsistency caused by the database alignment
Out of order Interruption of communication with the Supervision
Center.
Acronym incongruity Inconsistency caused by the database alignment
Data incongruity Inconsistency caused by the database alignment
Node incongruity Inconsistency caused by the database alignment
TemaServer begin defrag The database defragmentation started.
Dial-up established The dial-up connection is on (EBI).
Dial-up interrupted The dial-up connection has been interrupted.
Battery level < 10% Level of internal battery is below 10%.
Battery level < 25% Level of internal battery is below 25%.
115
Event Description
Battery low level Level of internal battery is low.
No electrical supply Event related to an error on the electrical supply.
Primary voltage failure A power failure was detected on the network.
Disable panel alarm relay The alarm relay on the ID panel is disabled.
Disable panel failure relay The failure relay on the ID panel is disabled.
DB Reset The reset of the TemaServer database has been
performed.
Reset DB required The Supervision Center required the DB download on the
TemaServer.
TemaServer reset The TemaServer has been restarted and the database reset
has been performed.
Ring short A short circuit has been detected in the ring connection.
Switched off The ID panel has been switched off due to a power failure
on the network and the battery failure.
Table size exceeded Inconsistency caused by the database alignment
Ring cut A cut has been detected in the ring connection.
Disable panel tamper The tamper on the ID panel is disabled.
Telnet enabled The Telnet connection has been enabled.
Timeout to receive ACK Inconsistency caused by the database alignment
Upload not allowed The TemaServer has not been prepared via Telnet, so it is
not ready for the upload.
Upload failed An error occurred during the upload procedure. This
event is generated by the Supervision Center.
PLANT
Plant
Plant statuses

NOT DETECTED 0 The Supervision Center does not
have information regarding the status
of the device. It is possible that the
Sky Blue communication management process
is not running.
MAINTENANCE 4 The Maintenance working mode has
been set for the plant.
Green
GENERAL TESTING 5 The General Testing working mode
has been set for the plant.
Green
IN TEST 2 The test on all zones of the plant is in
progress.
Viola
DISARMED 1 At least one zone of the plant is
disarmed. It will not send any alarm
to the Supervision Center.
Blue
ARM/ NORMAL 3 The plant is armed and operating
normally.
Green
Gray temporarily interrupted.
117
Commands on the Plant
Command Description EBI EBI Value

Parameter
Status Request Requests to the TemaServer the current Commands 1
status of the object.
Disarm Disarms the plant for all zones that make Commands 6
it up.
Arm Arms the plant and all zones that make it Commands 7
up after running the test. When the plant
is armed, it is authorized to send alarms
to the Center.
Test all zones Runs the test for all zones of the plant and Commands 2
for their associated detectors, and checks
the level of charge on the batteries.
Overtime booking Books the overtime for all zones of the Commands 3
plant configured for this feature.
Restore Interrupts all feedbacks in progress and Commands 5
restores all the reset type outputs on the
TemaServer ID that manages the plant.
Set to maintenance Sets the maintenance working mode for Commands 8
the plant.
General Testing Sets the general testing working mode for Commands 9
Mode the plant.
Operational Mode Sets the operational working mode for Commands 10
the plant.
Alarms List Acknowledges the peripheral alarm list Commands 11
Acknowledge for the plant.
Alarm List Deletion Deletes the peripheral alarm list for the Commands 12
plant.
Reset Plant Arm Restores the armed status for all zones of Commands 13
Status the plant.
Events generated by the Plant
Event Description
Disarmed The plant has been disarmed. No events will be sent to the
Supervision Center.
Test OK The test succeeded. An event is raised only if the test on
the plant is run manually (not when arming the plant).
PLANT
Event Description
Test failed The test on one of the zones of the plant did not succeed.
Modify password validity The password validity dates for an operator have been
changed.
Password reset The starting password of the operator has been reset.
Start maintenance mode The maintenance working mode has been set for the plant.
Start general testing mode The general testing mode has been set for the plant.
119
Miniterminal
Miniterminal statuses

NOT DETECTED 0 The Supervision Center does not
have information regarding the status
of the device. It is possible that the
Sky Blue communication management process
is not running.
NORMAL The device is in normal status.
Green
OUT OF SERVICE The miniterminal is out of order.
Communication between the
TemaServer and the RTU
Yellow components that make up the
miniterminal has been interrupted or
the RTU detected a tamper condition.
Gray temporarily interrupted.
Commands on the Miniterminal

Parameter
Green ON Turns on the green LED. It applies to the Commands 2
Reader and Keyboard miniterminal
types; this command is not available on
the miniterminal display, but only via
feedback.
MINITERMINAL

Parameter
Red ON Turns on the red LED. It applies to the Commands 3
feedback.
Led OFF Turns off the LED. It applies to the Commands 4
feedback.
Events generated by the Miniterminal
Event Description
Out of order Interruption of communication with the TemaServer.
User Login The miniterminal has been logged on.
User Logout The miniterminal has been logged out.
Wrong Password A wrong password has been specified.
User expired The operator validity dates are expired.
User disabled The operator attempting the login has been disabled.
Login under duress An attempt has been made to force the login.
Change Password The password that allows the operator to access the
miniterminal has been changed.
Activation OK It only applies to MT Readers and MT Keyboards: the
execution of the activation was successfully performed.
Activation Not OK It only applies to MT Readers and MT Keyboards: the
execution of the activation failed because the operator
does not have the required rights.
121
Detector
Detector statuses

NOT DETECTED 0 There are two possible scenarios:
• Communication between the
Supervision Center and the
Sky Blue TemaServer that manages the
detector has been interrupted
(status assigned by the Supervision
Center).
• Communication between the RTU
that manages the detector and the
TemaServer has been interrupted
(status assigned by the
TemaServer).
DISABLED 1 The detector is disabled and no alarms
will be generated.
Sky Blue
DISARMED 4 The detector has been disarmed. It will
no longer send activate/deactivate
events; it will only send technical type
events (cut, short circuit).
Blue
DE-ACTIVATE 8 The detector is surveyed, enabled and
armed, and no alarm condition has
been detected.
Green
PRE-ALARM 9 The detector is in pre-alarm.
Yellow
DETECTOR

ALARM 5 The detector is in alarm. The Alarm
status normally generates alarms when
the detector is armed; for the detector
with Alternative Behavior, it
indicates that the detector has been
Orange activated while it was disarmed.
TAMPER ALARM 6 Safety management related status. It

indicates that the device is open.
Red
CUT ALARM 3 The link between the detector and the
connecting device has been cut.
Yellow
SHORT CIRCUIT 2 The detector has detected a short
ALARM circuit condition.
Yellow
UNDER TEST 7 The test on the detector is in progress.
Green
ACTIVATE 10 The device has been activated. This
state is used for detectors with
Alternative Behavior and indicates
that the detector has been activated
while in armed status.
Green
Gray
123
Commands on Detectors

Parameter
Disarm Disarm the detector. This command Disarmed 1
cannot be used on an individual detector
that is associated with a zone.
Arm Arm the detector. All alarms will be Disarmed 0
generated. This command cannot be used
on an individual detector that is
associated with a zone.
Disable Sets the detector to Disabled status. In Disabled 1
this status, a detector will not generate
alarms. This command may only be
executed if the maximum number of
disabled detectors has not been reached
within the zone to which the detector
belongs.
Enable Returns the detector from the status of Disabled 0
Disabled to the previous status of
Enabled.
Test Starts the test procedure for the detector, Commands 3
provided that this feature has been
enabled in the configuration.
Reset Resets the detector, meaning it returns it Commands 4
to the normal status, provided that this
feature has been enabled in the
configuration.
Events generated by Detectors
Event Description
Out of order RTU component that manages the detector is in failure.
Disabled The detector has been disabled. No event will arrive from
the terminal during this phase.
Enabled It is used to keep the “Enabled” event (that is, the return
event for the “Disabled” emission alarm) within the alarm
list even if the emission alarm has been acknowledged.
DETECTOR
Event Description
Disable failed The disable command failed because the max. number of
detectors within the zone that may be disabled has been
reached.
Disarmed The detector has been disarmed and will not transmit
enable/disable events. It will only transmit events of a
technical nature (cut, short circuit).
Active The detector has been activated. This alarm is used for
detectors with Alternative Behavior to indicate that the
detector has been activated/deactivated while in armed
status.
Alarm The detector is in alarm.
Pre-alarm The detector is in pre-alarm. This event applies to
detectors that are configured for pre-alarms management.
Cut alarm Indicates that the detector connection has been cut.
Short circuit alarm Indicates a short condition for the detector.
Tamper alarm An attempt has been made to open the device.
Test OK The test on detector succeeded. This event is raised only if
the test has been run on an individual detector; it will not
be raised if the test has been run on the associated zone or
on the plant.
Test failed The test on detector did not succeed.
125
Output device
Output Devices statuses

TemaServer that manages the
output has been interrupted (status
Sky Blue assigned by the Supervision
Center).
• Communication between the RTU
that manages the output and the
TemaServer has been interrupted
(status assigned by the
TemaServer).
DISABLED 1 The output is disabled and no alarms
will be generated.
Sky Blue
DISARMED 2 The output is disarmed. It will no
longer send activate/deactivate events;
it will only send technical type events
(cut, short circuit).
Blue
ACTIVATE 3 The output is activated.
Orange
DE-ACTIVATE 4 The Output is enabled, armed and
deactivated.
Green
OUTPUT DEVICE

- Insignificant value. The chain of
BAD POINT applications/communication devices
Gray
Commands on Digital Outputs

Parameter
Arm Arms the output device. Disarmed 0
Disarm Disarms the digital output. This Disarmed 1
command cannot be used on an individual
output that is associated with a zone.
Disable Sets the “Disabled” status for the output. Disabled 1
It will no longer generate alarms.
Enable Resets the “Enabled” status for the digital Disabled 0
output.
Activate Activates the digital output. Activate 1
Deactivate Deactivates the digital output. Activate 0
Events generated by Digital Outputs
Event Description
Out of order The RTU component responsible for controlling the
output device is in failure.
Disabled The output has been disabled. No event will arrive from
the terminal during this phase.
Disarmed The output has been disarmed and will not send enable/
disable events. It will only send events of a technical
nature (cut, short circuit).
127
Event Description
Activate The output has been activated.
Alarm The output is in alarm status.
INTRUSION ZONES
Intrusion Zones
Intrusion Zone statuses

NOT DETECTED 0 Communication between the
TemaServer that manages this zone
has been interrupted (status assigned
by the Supervision Center).
Sky Blue
DISABLED 1 The zone is disabled and no alarms
will be generated.
Sky Blue
DISARMED 6 The zone is disarmed. The detectors
and output devices associated with the
zone will not send activation/
deactivation events.
Blue
UNDER TEST 2 The zone is under test.
Green
WAIT CONFIRM 5 Waiting for the operator to confirm.
For semi-automatic or confirmable
zones.
Green
OVERTIME BOOKED 4 The overtime for the zone has been
booked.
Yellow
129

DELAYED ARM 3 The delayed arm for the zone is in
progress.
Green
- Insignificant value. The chain of
BAD POINT applications/communication devices
Gray
Commands on Intrusion Zones

Parameter
Disarm Disarms the zone and all the associated Disarmed 1
detectors and digital outputs for intrusion
detection. Manual disarming is possible
within the context of the time scheduling
defined for the zone, and in accordance
with the management mode set for the
zone.
Arm Arms the zone and all the associated Disarmed 0
detectors and outputs.
Disable Sets the zone to Disabled status. In this Disabled 1
status, a zone will not generate alarms.
Enable Returns the zone from the status of Disabled 0
Disabled to the previous status of
Enabled.
Overtime booking Books the overtime for the zone, if this Commands 3
feature has been enabled for the zone.
Test Starts the test procedure for the zone and Commands 2
for all the detectors associated with it (if
the zone has been so configured via the
Supervision Center).
Reset Zone Arm Restores the armed status for the zone; Commands 5
Status the zone will be re-armed based upon the
plant schedule for arming/disarming.
INTRUSION ZONES
Events generated by Intrusion Zones
Event Description
Disarmed The zone has been disarmed.
Disabled The zone has been disabled. No event will arrive from the
terminal during this phase.
Max disabled detectors The maximum number of detectors that can be disabled in
a zone has been reached.
Test OK The test on the zone succeeded. This event is raised only
if the test on the zone has been run manually (not when
arming the zone or the plant).
Test failed The test on the zone did not succeed.
131
Logic
Logic statuses

TemaServer that manages the logic
Sky Blue has been interrupted (status
assigned by the Supervision
Center).
• One or more items that compose
the logic are in “Not Surveyed”
status (status assigned by the
TemaServer).
ALARM 1 One or more items that compose the
logic is in alarm.
Red
DISARMED 2 The logic is disarmed. All detectors
that are associated with it will not send
any activation/deactivation signal.
Blue
ARMED 3 The logic is armed and is working
properly.
Green
Gray
LOGIC
Commands on Logics

Parameter
Disarm Disarms the logic. The detectors Disarmed 1
associated with this logic will no longer
generate enable/disable events and will
only generate technical alarms (cut and
short circuit).
Arm Arms the logic. Disarmed 0
Events generated by Logics
Event Description
Disarmed The logic has been disarmed.
Alarm The logic is in alarm status.
133
Conformity to the CEI 79-2
Rules 8
This chapter describes the special requirements to which the Tema ID Panel must
comply in order to be compliant with the CEI 79-2:1988 Rules.
The following table summarizes the objects to which the Rules refer, together
with the relative section within the Guide, and the requirement/restriction to be
applied, otherwise the relevant IMQ-SECURITY SYSTEMS Certification will be
cancelled:
Section in the Guide Object/Matter Requirement/Restriction

Memory Formatting Storing events see Events are stored in a circular buffer
display IEVENBUF in the section into non-volatile memory (Flash.) In
on “Default intrusion this case, in order to satisfy the
database format” on Rules, the specified number of
page 52) events must be at least 64.
“Detectors display” Key type detector Detectors of Key type require a
on page 63 driving-gear that has the same
performance level as the ID Panel;
the card decoder, if any, must be
placed within the Panel.
Normality Value The normality value must be equal to
0.
135
8 – CONFORMITY TO THE CEI 79-2 RULES
Section in the Guide Object/Matter Requirement/Restriction

“Intrusion Digital General features for outputs • Only one output for alarm
Output display” on configuration devices can have an activation
page 72 delay of max. 1 second.
• You must configure one output
for tampering signals and one
output for alarm signals with
which the main alarm devices are
connected. The general alarm
relay connected to the ID Panel is
responsible for alarm signals,
while, as far as concerns the
tampering signals, a specific
output shall be configured which
will be activated via a feedback.
“Intrusion Zones Configuring the overtime The value set for both the Break
display” on page 28 for a zone Overtime and the End Overtime
fields cannot exceed 180 minutes.

EBI R610.1 ID - Guide

Uploaded by

Copyright:

Available Formats

EBI R610.1 ID - Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBI R610.1 ID - Guide

Uploaded by

Copyright:

Available Formats

EBI Temaline Interface

Intrusion Detection Module Guide

2 Intrusion configuration overview 11

Logics - Configuration tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Intrusion Digital Output - Main tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

6 Point detail displays - ID 89

Point Detail display - Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

7 Statuses, Commands, and Events 109

8 Conformity to the CEI 79-2 Rules 135

Chapter Contents See

Chapter Contents See

Intrusion subsystem architectures

Tema SEC architecture

Intrusion system composition

Component Max. Notes

Component Max. Notes

Access the intrusion configuration displays

2 Click the desired configuration display.

Work with the configuration displays

Topic Explains how to...

Topic Explains how to...

To learn about Go to:

To learn about Go to:

Open the Plants display

Plants - Main tab

Plants - Security tab

Plants - Feedback tab

Plants - Supervision tab

Plants - Alarm Settings tab

5 In the Description box, type in a description for the new plant.

Credential Types display

To learn about Go to:

Open the Credential Types display

Reading technologies managed by intrusion detection

Define the credential type for intrusion

Intrusion Zones display

Open the Intrusion Zones display

Intrusion Zones - Main tab

Intrusion Zones - Arm/Disarm tab

Zone management types

Zone management type Example

Zone management type Example

Intrusion Zones - Test tab

Intrusion Zones - Others tab

Intrusion Zones - Supervision tab

Intrusion Zones - Alarm Settings tab

To learn about Go to:

Open the Logics display

Logics - Main tab

Logics - Configuration tab

Logics - Behavior tab

Logics - Supervision tab

Logics - Alarm Settings tab

Example of logical correlation

Save data for several logics

For more information refer to:

Operative Notes display

Open the Operative Notes display

Operative Notes - Main tab