Pronet Plus User Manual
Pronet Plus User Manual
Pronet Plus User Manual
Table of Content
1. WELCOME........................................................................................................................................... 6
1.1. ABOUT PRONET PLUS ................................................................................................................... 6
1.2. MONITORING TOOL ........................................................................................................................... 6
1.2.1. Access Control .......................................................................................................................... 6
1.2.2. Alarm Management................................................................................................................... 7
1.2.3. Lift Management ....................................................................................................................... 7
1.2.4. Parking Management................................................................................................................ 7
1.2.5. Time & Attendance Management.............................................................................................. 7
1.3. TYPES OF INSTALLATIONS ................................................................................................................. 7
1.4. MODULES .......................................................................................................................................... 8
1.4.1. Database ................................................................................................................................... 8
1.4.2. Communication ......................................................................................................................... 8
1.4.3. Operation .................................................................................................................................. 8
1.5. BASIC CONFIGURATION..................................................................................................................... 8
1.5.1. Operating System and Computer .............................................................................................. 8
1.5.2. Controllers ................................................................................................................................ 8
1.5.3. Readers ..................................................................................................................................... 8
1.5.4. Other Materials......................................................................................................................... 9
1.6. GENERAL USE OF PRONET PLUS ................................................................................................... 9
1.6.1. First Installation ....................................................................................................................... 9
1.6.2. Demonstration Version ............................................................................................................. 9
1.6.3. Plug ......................................................................................................................................... 10
1.6.4. Running PRONET PLUS ........................................................................................................ 10
1.6.5. Modifying Data Entry ............................................................................................................. 11
1.6.6. New Data Entry....................................................................................................................... 11
1.6.7. Exiting the Application............................................................................................................ 12
1.6.8. Update an PRONET PLUS version ........................................................................................ 12
1.6.9. PRONET PLUS Database Protection..................................................................................... 12
2. GENERAL SCREENS ....................................................................................................................... 13
2.1. MAIN SCREEN ................................................................................................................................. 13
2.2. TOOL BAR ....................................................................................................................................... 14
2.3. SCROLLING MENUS ......................................................................................................................... 14
2.4. NAVIGATION BAR ........................................................................................................................... 15
2.5. PERSONALIZED NAVIGATION BAR .................................................................................................. 15
3. PARAMETER MENU.................................................................................................................... 16
3.1. COMPUTER ...................................................................................................................................... 16
3.2. CONTROLLER NETWORK ................................................................................................................. 17
3.2.1. Controller Network - General................................................................................................. 17
3.2.2. Controller Network - Definition.............................................................................................. 18
3.2.3. Controller Network, advanced settings................................................................................... 21
3.3. CONTROLLER .................................................................................................................................. 24
3.3.1. Controller - General ............................................................................................................... 24
3.3.2. Controller - Readers ............................................................................................................... 26
3.3.3. Controller - Input .................................................................................................................... 40
3.3.4. Controller - Output ................................................................................................................. 43
3.3.5. Controller - Local Reflexes ..................................................................................................... 45
3.4. TIME ZONE ...................................................................................................................................... 47
3.4.1. Basic Concepts........................................................................................................................ 47
3.4.2. Daily Program ........................................................................................................................ 48
3.4.3. Weekly Program...................................................................................................................... 49
3.4.4. Holiday.................................................................................................................................... 50
2 PRONET PLUS User Manual
3.5. ACCESS GROUP ............................................................................................................................... 51
3.6. DEPARTMENT .................................................................................................................................. 52
3.7. BADGE ............................................................................................................................................ 53
3.7.1. Badge Search .......................................................................................................................... 55
3.7.2. Group of Badges ..................................................................................................................... 56
3.8. ALL CARDHOLDERS ......................................................................................................................... 58
3.8.1. All cardholders - Basic Concepts............................................................................................ 58
3.8.2. All cardholders - General ....................................................................................................... 58
3.8.3. All cardholders - Badge Printing Module............................................................................... 62
3.8.4. All cardholders - Biometrics data........................................................................................... 63
3.8.5. All cardholders - Personal...................................................................................................... 65
3.8.6. All cardholders - Location ...................................................................................................... 66
3.8.7. All cardholders - Customized.................................................................................................. 66
3.8.8. All cardholders - Exceptions................................................................................................... 67
3.8.9. All cardholders - Schedule AG................................................................................................ 67
3.9. VISITOR ........................................................................................................................................... 68
3.10. MULTI COMPANY MODULE ........................................................................................................... 69
3.10.1. Multi Company Module - Basic Concepts ............................................................................ 69
3.10.2. Company ............................................................................................................................... 70
3.10.3. Super-User ............................................................................................................................ 70
3.10.4. Shared Information ............................................................................................................... 71
3.11. AUTHORIZATION LEVELS .............................................................................................................. 72
3.12. USER ............................................................................................................................................. 73
3.13. CUSTOMISED LABELS AND FIELDS ................................................................................................ 74
3.14. LOG OFF........................................................................................................................................ 74
3.15. EXITING THE APPLICATION ........................................................................................................... 74
4. EVENT HANDLING MENU......................................................................................................... 75
4.1. ICON ................................................................................................................................................ 75
4.2. MAP ................................................................................................................................................ 76
4.2.1. Map - General......................................................................................................................... 76
4.2.2. Map - Icon............................................................................................................................... 76
4.3. POSITION ......................................................................................................................................... 77
4.4. INPUT GROUP .................................................................................................................................. 78
4.4.1. Input Group - General ............................................................................................................ 78
4.4.2. Input Group - Inputs ............................................................................................................... 80
4.5. OUTPUT GROUP ............................................................................................................................... 81
4.6. ACTION ........................................................................................................................................... 82
4.7. PROCESS .......................................................................................................................................... 84
4.8. COUNTER ........................................................................................................................................ 85
4.9. GLOBAL REFLEX ............................................................................................................................. 86
4.9.1. Global Reflex - Basic Concepts .............................................................................................. 86
4.9.2. Global Reflex - General .......................................................................................................... 87
4.9.3. Global Reflex - Properties ...................................................................................................... 88
4.10. EVENT-HANDLING PROGRAM ....................................................................................................... 90
4.10.1. Event-Handling Program - Basic Concepts.......................................................................... 90
4.10.2. Event-Handling Program - General ..................................................................................... 90
4.10.3. Event-Handling Program - Alarms....................................................................................... 91
4.10.4. Event-Handling Program - Alarm Properties ...................................................................... 92
4.10.5. Event-Handling Program - Global Reflexes......................................................................... 93
4.11. ACTIVE ALARMS ........................................................................................................................... 94
4.11.1. Active Alarms - Basic Concepts ............................................................................................ 94
4.11.2. Active Alarms - Map ............................................................................................................. 95
4.11.3. Active Alarms - Input Status.................................................................................................. 99
4.11.4. Active Alarms - Output Status............................................................................................. 101
PRONET PLUS User Manual 3
5. MODULES MENU ....................................................................................................................... 102
5.1. PARKING MODULE ........................................................................................................................ 102
5.1.1. Parking Module - Basic Concepts ........................................................................................ 102
5.1.2. Parking Lot ........................................................................................................................... 104
5.1.3. Parking Users Group ............................................................................................................ 105
5.1.4. Parking Zone......................................................................................................................... 106
5.1.5. Reset Parking Zones ............................................................................................................. 108
5.2. LIFT MODULE................................................................................................................................ 109
5.2.1. Lift Module - Basic Concepts................................................................................................ 109
5.2.2. Lift Program.......................................................................................................................... 110
5.2.3. Lift Authorization Group....................................................................................................... 112
5.3. TIME & ATTENDANCE MANAGEMENT MODULE ........................................................................... 113
5.3.1. Roll Call ................................................................................................................................ 113
5.4. GUARD PATROL MODULE ............................................................................................................. 114
5.4.1. Guard Patrol Module - Basic Concepts................................................................................ 114
5.4.2. Guard .................................................................................................................................... 114
5.4.3. Checkpoint - General ............................................................................................................ 114
5.4.4. Guard Tour Program ............................................................................................................ 115
5.4.5. Guard Tour Status................................................................................................................. 116
5.4.6. Patrol Report......................................................................................................................... 117
5.5. VIDEO MODULE ............................................................................................................................ 118
5.5.1. Video Module - Basic Concepts ............................................................................................ 118
5.5.2. Video Module - DVR ............................................................................................................. 120
5.5.3. Video Module - Camera........................................................................................................ 120
6. COMMUNICATION MENU....................................................................................................... 121
6.1. STOP / RESUME POLLING ............................................................................................................... 121
6.2. DIAGNOSE ..................................................................................................................................... 121
6.3. VIEW / CLEAR LOG........................................................................................................................ 124
6.4. DISPLAY PHOTO ............................................................................................................................ 125
7. MANUAL ACTION MENU ........................................................................................................ 126
7.1. CRISIS LEVEL ................................................................................................................................ 126
7.2. RELAYS CONTROL ......................................................................................................................... 128
7.3. EXECUTE PROCESS ........................................................................................................................ 129
8. TOOLS MENU.............................................................................................................................. 130
8.1. REPORT WIZARD ............................................................................................................................ 130
8.1.1. Report wizard - Basic Concepts............................................................................................ 130
8.1.2. Report wizard - Step 1 / 4: Report Selection......................................................................... 130
8.1.3. Report wizard - Step 2 / 4: Data Selection............................................................................ 133
8.1.4. Report wizard - Data Viewing .............................................................................................. 134
8.1.5. Report wizard - Step 3 / 4: Data Filtering ............................................................................ 135
8.1.6. Report wizard - Step 4 / 4: Data Organization..................................................................... 136
8.2. CREATE NEW DATABASE .............................................................................................................. 137
8.3. SAVE DATABASE ........................................................................................................................... 137
8.4. RESTORE DATABASE ..................................................................................................................... 138
8.5. SWITCH DATABASE ....................................................................................................................... 139
8.6. CREATE NEW JOURNAL ................................................................................................................. 139
8.7. SAVE JOURNAL.............................................................................................................................. 140
8.8. RESTORE JOURNAL ........................................................................................................................ 141
1.4.2. Communication
The communication module coordinates the data transfer between the main computer and the
controllers that detect the events. The information collected is recorded in the journal and
displayed in the log.
1.4.3. Operation
The operational module interprets information collected by the communication module. Its role
is to activate predefined tasks such as alarms, reflexes, etc.
The events to consider, and the resulting actions, are specified in the different screens of the
Event Handling section.
Operating system:
Windows 2000 Pro or Windows XPRO or Windows 2003 Server
The manufacturer recommends these two operating systems and is not responsible for errors
occurring while using other operating systems.
Computer:
Pentium IV minimum
256 MB RAM (or 1 GB RAM for installations with more than 100 controllers or with SQL Server)
500 MB free hard disk space
CDROM Drive
1 free serial COM port and 1 parallel port or USB port
Recommended enhancement:
Sound Card , Speakers , SVGA definition (800*600)
1.5.2. Controllers
All ACTEC controllers for on-line networks are compatible with PRONET PLUS.
1.5.3. Readers
The vast majority of readers available on the market are compatible with the PRONET PLUS
system: magnetic, proximity, bar code, smart card, biometry, Wiegand, contact, infrared,
keypad, etc.
Consult with your PRONET PLUS reseller for further information.
8 PRONET PLUS User Manual
1.5.4. Other Materials
In order to successfully install and run the PRONET PLUS system, other materials are
required. These vary according to each installation: computer network, devices to open doors,
alarm detectors, etc. Consult with your PRONET PLUS provider for further details.
Note: This product uses software developed by Spread Concepts LLC for use in the Spread
toolkit. For more information about Spread see http://www.spread.org.
Database type:
During the installation, the user is asked to select the database format: Access or SQL. If
SQL has to be requested, ensure first that the Microsoft SQL server or MSDE (the SQL
server engine) is already running in the computer or in the network and the PRONET PLUS
plug has the SQL license.
nC: Maximum No. (n) of Controllers allowed T: Time & attendance Module
nR: Maximum No. (n) of Readers allowed M: Multi-company Module
nB: Maximum No. (n) of Badgeholders allowed U: Guard patrol Module
nW: Maximum No. (n) of Workstations allowed O: OPC Server Module
A: Alarm Module SQL: MS-SQL database support
G: Graphic Module BP: Badge Printing Module
P: Parking Module V : Video Module
L: Lift Module
NetHasp = 1
If this line does not exist, run the application, go to Tools - Options and click OK. This
operation rebuilds the ini file and inserts all the possible entries according to the latest
application version.
Set the value to 1
Save and close this file, then restart PRONET PLUS.
Emptying fields
By clicking on the New icon all the fields are cleared away or set to their default value to allow
new data entry.
Tutorial
The help screen is available from any screen by pressing the F1 function key and displays
explanations of the current screen.
Reminding of consulted screens
The fields of the scrolling menus in the main screen appear in black before use. However after
consultation, they appear in blue.
Multi-Windows
Several windows can be opened simultaneously.
Authorization Level
The options displayed depend on the authorization level of the user. Certain options are not
suitable for certain users and therefore do not appear on the screen.
Dissociating the alarm log from the access log
By default, a single log shows access, alarms and system messages. It is possible to
dissociate the alarm log from the access log, in the Options Tools Journal / Log screen
screen.
These menus are those of the Version 1.5.002. New ones may be added on further versions.
The function keys correspond to the icons on the navigation bar are discribed here after. They
are available from each capture screen.
F2 New Define a new data entry
F3 Save Save the current data information
F4 Delete Delete the data selected
F5 First Select the first data entry of the list
F6 Previous Select the previous data entry
F7 Next Select the next data entry
F8 Last Select the last data entry of the list
F9 Download Transfer all the parameters to the corresponding controllers even if the
information has not been modified
F10 Search Look for the desired data in the list
F11 Print Generate automatically the report corresponding to the current data
F12 Close Close the screen and return to the previous screen
Tutorial
F1 Help Display the help screen of the current screen
New Data
By clicking on the F2 key, the fields of the newly created item are empty to allow entry of new
data. If existing information has not yet been saved, a message appears requesting the user to
save or cancel the changes. Saving (F3 key) transfers automatically the modified parameters
to corresponding controllers.
Fields
Fields
Fields
Fields
Fields
Fields
Fields
Bus 2: When the Controller Network is defined as Bus 2, this bus must be connected to the
secondary serial port (Connector J10) of all the controllers equipped with a second RS485
communication port. ((U29) and (U30) components must be present on the controller board).
This bus may have three different uses. Check the option box for which this bus must be used:
Redundant bus: Backup communication bus for acting as an alternative communication
bus for the controller in case of main communication port failure (connected to a TCP/IP
network, for example). If this option is set, then when the PRONET PLUS detects a
communication error with one or more controllers of the network, it swaps the
communication of all the controllers of that network to Bus 2. This change is done after
the Communication error time out delay (30 sec. by default, changeable in the Tools -
Options - Communication screen). At that point the communication will continue on the
secondary bus. However, maximum 5 minutes later, PRONET PLUS will test the main
bus: if all the controllers answer, the main bus is automatically restored; otherwise,
communication will continue on the Bus 2 for another 5 minutes. This feature is
required the use of EPROM TPL from 03/09/2002 or later.
Fields
Active: 5: to activate communication (parameters download and polling) with the controller.
: to disengage communication between the PC and the controller. Polling is not
done in this case; the controller is not polled and is not downloaded by the system.
Set as default: Check the box if the current controller should serve as a reference. Its
parameters are automatically copied as default parameters for newly created controllers, thus
preventing to have to parameter newly created future controllers.
Company: Company the item refers to (for use with multi-company application ONLY).
Controller address:
Network: Select an existing network from a list of previously defined networks or create
a new network by clicking on the [] button.
Controller address (00-31): Mention the physical address of the controller in the
selected network. The address is contained between 00 and 31; it is defined on the
controller itself by the position of the address selection dip switches.
Controller type: Select the type of controller in the displayed list. This will enable PRONET
PLUS to set all the parameters (readers, inputs and outputs) with their default values,
according to the type selected.
Table analysis
Name: Reader name
Door alarm: Name of the input
signalling the closure of a door
Relay 1: Name of the first output
in the system
Weekly program: Weekly
program that automatically flip-
flops the way the reader operates
between the two security levels
Button [] (on the line of the
reader): Click on the button to
display the Reader screen for
creating, consulting or modifying
data
Button [2] (on the line of the
reader): Click on this button to
remove a reader from the line
Button [] (outside the table): Click on the button to display the Reader screen even if no
record is selected
Fields
Motorized Reader
It is possible to use the ACTEC magnetic motorized readers by selecting the Motorized
Reader technology in this screen. Two additional fields are displayed: in the first, select the
controller input connected to the badge detection signal (S1). In the second, select the
controller relay to which the Common is connected to the signal (MFC/MRC) that controls the
sense of the reader motor.
Wiegand, Wiegand 2 and Wiegand Keypad Technologies
When several readers are defined with a same technology, they must have the same badge
format. If some readers need a different format from the current badge format (i.e. a different
Wiegand format), their technology must be different and they must be connected on a different
controller.
The Wiegand reader technologies (Wiegand, Wiegand 2 and Wiegand Keypad) allow to
choose up to three different Wiegand format type. This helps for instance on sites where one
or more controllers support biometric readers and other controllers support other Wiegand
readers.
Example:
A site has 2 readers; each one is connected on a different controller:
Reader 1 / Controller 1 is a Bio-pass,
Reader 1 / Controller 2 is a simple Wiegand reader.
In this case, if a cardholder needs to pass on both readers, he may have two badges: one
Wiegand badge (to be used on the BioPass reader defined as Wiegand) and one
Wiegand2 badge (for the other reader defined accordingly). The PC will download cards of a
defined technology only to readers of the same technology. Wiegand cards to Wiegand
readers, Wiegand2 cards to Wiegand2 readers, etc.
Fields
Inputs:
Door alarm: Select the controller input to which the door opening control device is wired;
an alarm is set off when a door is forced or stays open beyond a predefined delay
Feedback: Check the box in order to verify the physical entry or exit of a badge holder that
has been granted access
Operation mode: A badge holder swipes his badge through a reader. The controller
authorizes access to the badge holder by activating a door relay. During the predefined
door alarm delay, during which the door can be opened, the controller goes into a waiting
mode. If the door has been opened and closed - as will attest the door opening control
device activation - the badge holder is supposed to have passed and the controller records
the access transaction in memory. If the door has not been opened, the door opening
control device is not activated and the controller records the transaction access refused
in memory.
APB level (for Global Anti-Passback function):
From: Select a reader APB level to be the Previous level of the reader from the list or
click on the [] button to define a new APB level
To: select a reader APB level to be the Actual level of the reader from the list or click on
the [] button to define a new APB level
Operation mode: See the Global Anti-Passback function in the next paragraph.
Outputs:
First and Second Outputs: Select the relays to be activated upon a granted access.
Door type: Select from the list:
Standard: Access is granted if badge is authorized
Controlled by Input: A door is controlled by the status of an input. Specify the input in
question in the Controlled by field. the door opens if the input is inactive but remains
closed if the input is active. (If, for example, the input selected is a second door alarm
input, the door will be opened only if this second door is closed)
Man Trap 1, 3, 4: Select if the doors operate in the man trap mode, which means that the
passage through two consecutive doors is a requisite in order to access a site.
Manually Controlled: Access is manually regulated
PRONET PLUS User Manual 29
Note on the Mantrap mode:
The man trap mode supervises the activation process of a double door entrance. The first door
opening and the possible activation of an input are the conditions for the opening of a second
door.
PRONET PLUS supervises three types of man traps:
Man trap 1: The first door will open only if the second door is closed. Both readers of a
same controller monitor two doors (reader 1 with reader 2 or reader 3 with reader 4). The
door of each reader must be defined as Man trap 1. When access is granted at a reader,
this reader is locked untill the personn passes through the second door. The door
opening control device status attests to the opening or closure of doors.
Man trap 3: The second door opens automatically following the opening and closure of
the first door. Both readers of a same controller monitor two doors (reader 1 with reader 2
or reader 3 with reader 4). The door of each reader must be defined as Man trap 3.
When the first door opens and closes the second door automatically opens. The door
opening control device status attests to the opening or closure of doors.
Man trap 4: The second door automatically opens consecutively to the following two
conditions:
Opening and closure of the first door and
Receipt of a signal - activation of an input
Both readers of a same controller monitor two doors (reader 1 with reader 2 or reader 3
with reader 4). The door of each reader must be defined as Man trap 4. When the first
door opens and closes, and a predefined input is activated, the second door opens
automatically. The required input must be defined in the Controleld by field. The door
opening control device status attests to the opening or closure of doors.
Example
During office hours, access is freely granted (no need to swipe a badge). After office hours,
badges need to be swiped (controlled door).
Fields
Card issue reader: Select this option to create new badges using a reader. If the reader is in
the card issue reader mode, it cannot be used for access control purposes.
The card issue reader is generally situated close to the computer. When a badge is read, its
code is directly transmit to the PC for recording purpose, without any authorization checks, and
this to prevent the small waiting delay this check may take.
Unsuccessful attempts: specify the number of successive unsuccessful attempts tolerated by
the system before an alarm is raised; choose a number from 00 to 99
Default Transaction code: specify the transaction code sent by the controller to the PC when
an access is granted; the user via the reader keypad can modify this code
Transaction code F1, F2, F3: attribute a specific transaction code to the keypad function keys
(if exist). This code is sent when access is granted and the function key was used.
Note: Pre-defined action(s) may be triggered by PRONET PLUS upon reception of specific
transaction codes. (Refer to Global Reflex Chapter)
Leave door relay open during all Door Open Time: If not selected (by default), the
controller deactivates the door relay as soon as it detects (through the door contact device)
that the door has been opened. Selecting this option will leave the relay activated during the
door open time.
Badge Format Fields: There are various formats of magnetic, bar code and Wiegand
technologies. By default the system reads the first 8 encoded numbers on magnetic or bar
code badges or the 8 hexadecimal digits of a Wiegand badge but this way of reading can be
modified. These fields allow to change this badge format.
Controllers may recognize many kind of badge technologies (Magnetic, Barcodes, Wiegand,
etc). The reading technology used must be specified in the Controller Reader General
screen.
Within a same technology, different formats may be defined through this Miscellaneous-Badge
format screen as described hereunder.
Fields
System card: Card on which a four-digit number between 0001 and 9999 has been inscribed;
since the card number is already on the badge, it enables immediate recognition of the badge
holder and therefore, a system badge need not be recorded up in the system.
Card code position: The card code is a unique code, which identifies the card. The system
records card code of 8 digits only. A bar code or magnetic code may contain many numbers or
characters; by default, the first 8 characters of the code are recorded as the card code. It is
possible however to read another 8-digit by specifying the position of the first one in the Card
Code Position field (Value between 0 and 37, the default value 0 corresponds to the first
encoded character).
Customer (or site) code: It is a same code, which appears on all the cards of a same
company, besides the badge code; the use of a customer code value is optional and
strengthens system security by identifying the company.
By the default this option is not used. To use it, fill out the following three fields:
Customer code position: Specify the position of the first character of the code; choose
a value between 0 and 37 (0 corresponds to the position of the first number encoded in
the badge).
Customer code length: Specify the size of the code to be read; choose a value
between 1 and 7. Note that 0 is the default value, which means that the customer code
value is not checked.
Customer code value: Enter the customer code value into the squares that appear on
the screen.
Wiegand technology:
When Wiegand technology is selected in the Controller Reader General screen, different
formats may be selected in the Controller - Readers - Miscellaneous/Badge Format screen.
Fields
E b47 . b b b b0 O
Where: b47 b0 = 48 bits of data maximum (may be less) and E,O = 2 parity bits
In this hexadecimal format, the system keeps as the card code the 32 least significant
bits of the data string (b31b0), in other words the last 8 digits of the code, which may
be hexadecimal.
Wiegand 44: Wiegand 44 format is a particular format of 44 bits, which includes 40 bits
of data (10 hexadecimal digits) and 4 parity bits, as follows:
b43 . b4 b3 b2 b1 b0
Decimal: This format is a particular format, where badge code consists on a 5 digits
decimal number (generally printed on the badge) sometimes associated with a 3 digits
decimal code site. ACTEC controllers may read a 50 bits Wiegand string as in the
hexadecimal format but convert the information in decimal as follows:
E b47 . b b b b0 O
Where: b15 b0 = 16 bits for card code, b23 b16 = 8 bits for site code and
E,O = 2 parity bits.
In this format, the system keeps as the card code the 16 least significant bits of the
data string (b15b0), in other words the last 4 hexadecimal digits of the code, and
converts them into a 5 digits decimal number, the unique code which identifies the card.
In addition, the system converts the 8 previous bits of the data string (b23b16), in other
words the 2 previous hexadecimal digits of the code, into a 3 digits decimal number
which may be used as a site code, an identical code for all the cards of the site.
If this site code has not to be checked, leave 0 in the Customer code length field. If
this code has to be checked (and therefore is present in all the cards of the site), select
the value 3 in this field and type the 3-digit code in the Customer code value field.
For example: If the Wiegand hexadecimal code is 12AB08, the site code is 018 (the
decimal value of h12) and the Card code is 00043784 (the decimal value of hAB08).
Decimal 24 bits: In this format, ACTEC controllers may read up to 50 bits Wiegand
string and convert it in two decimal numbers as per the Decimal format but the 3 digit
site code is add to the first 5 digits code. The 3 digit Site code may or may not be
checked as per the Decimal format.
For example: If the Wiegand hexadecimal code is 12AB08, the site code is 018 (the
decimal value of h12) and the Card code is 01843784 (43784 is the decimal value of
hAB08).
Operating Mode
Reader communication network and the reader address (written on the back of the
reader). Specify if the reader also serves for enrollment and set the Bio Wiegand format.
For BioPass readers and BioFlex readers with keypad, select the Standard 26 bits.
Note: On any given controller, all readers must be identical regarding the three following
points: Technology, Badge format, Bio Wiegand format.
Test the communication by opening the Diagnose screen (F8 function key): click on the
Biometric readers button, on the right top of the screen, then on the + symbol located a
the left of the network name and highlight the biometric reader created previously. The
communication is established if a V is displayed next to the reader name. Then, on the
right window, you can see the memory usage and the reader name with its address.
In the Parameter - All Cardholders - General screen, create a cardholder and define his
access authorization. Click on the Create new button for creating a badge. Save.
Note: To each cardholder, the system attributes two codes: the card code and the Bio ID
code (or Bio template ID).
From the Parameter - All Cardholders - General screen of this cardholder, press the
Biometrics data button. Select from the list the required enrollment reader and press the
Enroll button for a fingerprint enrollment. Follow the instructions displayed at the screen.
Once the enrollment is finished, an image of the fingerprint template is displayed on the
screen. To save it and to download it to the biometric readers, press Save. After the
template data is well received by the readers, the "Save" button is greyed out.
Fields
Note: A biometric reader can act as an enrolment reader in addition to its normal function as a
regular access reader.
Standard 26 bits format: The Bio ID is the decimal conversion of the last 4 hexadecimal
digits of the card code. This format allows also the Inverse parity and Duress code
features.
Standard 37 bits format: The Bio ID is the decimal conversion of the last 6 hexadecimal
digits of the card code. This format allows also the Inverse parity and Duress code
features.
Custom Pass-Thru format: A customized Bio format which allows the user to define
which bits to use in the Wiegand bits string to define the Bio ID. This format get three
parameters:
Total bits: Bits total number of the Wiegand card code read by the reader.
ID Start bit: First bit position of the Bio ID among the card code.
ID Length bits: Bits total number which compose the Bio ID.
Custom 6 digits format: The Bio ID is the decimal conversion of all the 6 hexadecimal
digits which compose the 26 bits card code.
Total bits = 26
ID Start bit = 1
ID Length bits = 24
Note: The calculation method used by the application to compute the Bio ID from the card code
depends on: (1) the Badge Format and (2) the Bio Wiegand Format.
If the Badge format and the Bio Wiegand format are the same for all the controllers and all the
biometric readers, the algorithm which links the card code and the Bio ID is the same for all the
system and therefore the cardholders Bio ID are similar on all the biometric readers. The
templates and their Bio ID numbers may be broadcasted to all the biometric readers.
Therefore, in a normal situation, it is recommended to have the same format definitions
throughout the whole system.
Table analysis
Num: Number of the selected
input
Name: Name of the input
Type: Mention if the input type
is Digital, Digital 4 states or
Analog.
Status: Input normal status, i.e.
normally open (NO), normally
closed (NC) or State 1 to 4.
Button [] (on the input line):
Click on this button to display
the Input screen for creating,
consulting or modifying data
Button [2] (on the input line):
Click on this button to remove
the input from the list displayed
Button [] (outside the table): Click on this button to display the Input screen even if no
input is selected
Fields
Name: Name the input
Number: Choose the input number;
the maximum input number
connectable depends on the type of
controller used (See Types of
controllers and associated readers,
inputs and outputs in the Controller
General Chapter)
Description: Describe the new data
entry
Input ON: Select the icon that
graphically represents the input in its
physically ON position in the maps
or click on the [] button for creating
a new one.
Input OFF: Select the icon that graphically represents the input in its physically OFF position
in the maps or click on the [] button for creating a new one.
Camera: Select the camera video to associate with this input, if needed (for use with the Video
Module ONLY).
Weekly program: Assign a program to the input to define alarm arming or disarming periods;
to create or modify the program, called also Event handling program, click on the [] button
(see also the Event Handling Program Chapter)
Input delay type:
No delay: An alarm is raised as soon as the input is activated
After (if on alarm): Specify the number of seconds beyond which an alarm is raised if
the input is still activated
After (even if no more on alarm): Specify the number of seconds beyond which an
alarm is raised, even if the input is not activated
Input type:
Digital (2 states): The input may have two states only: open or closed, which
correspond to the two possible states of the sensor/detector connected to the input.
Digital 4 states: In addition to the two basic states of the sensor/detector (open or
closed), the input may detect two supplementary states which correspond to the status
of the line used to connect the sensor/detector to the input: line cut or line short.
Analog: The input can take different decimal values according to the sensor connected
to it (temperature, etc.) and triggers alarms or specific action when it reaches pre-
defined values (by default, three limit values are defined: 2 / 2.88 / 4).
Consult the controller documentation to check which type of inputs is available in the controller.
Status: Choose the status among: NO, normally open or NC, normally closed or State 1 to 4,
in which the input is NOT under alarm.
Data displayed
Latest action: Latest PC action sent
to this input (PC actions always
overwrite the input status as defined
by its weekly program).
Note: Such action may be sent
manually, through the Event-
Handling Active alarms screen or
automatically through a pre-defined
input group deactivation global reflex.
Last event date: Exact time of the
last physical event on this input. This
refers to a real event, (i.e., not a PC
action).
Last event type: Type (start/end of
alarm, line cut/short) of the last
physical event on this input. This
refers to a real event, (i.e., not a PC
action).
Input group: Input group to which the selected input belongs. This field is visible after
selecting Alarm definition for group of input option in the Tools - Options - General screen.
Note: Allocating an input to an input group is done at the Event Handling - Input group
screen.
Weekly program: The weekly program of the input group (the weekly program of the individual
input can be seen at the General tab of the input screen. In a case of a conflict between the
two, the individual weekly program has the higher priority). This field is visible after selecting
Alarm definition for group of input option in the Tools - Options - General screen.
Table analysis
Fields
Table analysis
Fields
Arming alarms
Refer to the Event Handling Program - Alarm paragraph for more information regarding how
to arm an alarm.
Importance of a proper definition
Properly defining time zones is essential for the system to work optimally.
It is highly recommended to successively specify the daily, weekly and holiday programs prior
to defining the other parameters of the system.
Maximum number of usable programs
Many daily, weekly and holiday programs can be created in the whole the system but each
controller may include a restricted number of usable programs (99 Daily Programs, 32 Access
Weekly Programs, 80 Event Weekly Programs and 60 holidays). An error message appears if
the limit of usable programs has been exceeded for a specific controller.
Fields
Name: Name the new daily program; examples: part-time AM, night team
Company: Company the item refers to (for use with multi-company application ONLY).
Description: Describe the new data entry
Time zones 1 - 2 (or 1 - 4): Define the limits of the 2 (or 4) time zones using the format XX:YY,
where X = hour and Y = minute
The ruler at the bottom of the screen gives the time frames in a visual manner.
The green frames represent the Green periods (4 maximum)
The red frames represent the Red periods (5 maximum)
Programs by default
The two daily programs Always and Never are defined by default. Their denomination can
be modified but the two programs can neither be erased or their contents modified.
New daily program
By default, the time frames for a new daily program are from 8 AM to12 AM and from 2 PM to 6
PM.
Fields
Programs by default
The two weekly programs WP Always and WP Never are defined by default. Their
denomination can be modified but both programs can neither be deleted nor modified.
Deactivating Holiday and Special Days
Holiday and special days daily programs can be defined as <usual daily program of the day> in
order to deactivate the rule of these specific days, for some employees if needed.
Fields
Fields
3.6. Department
A department is a functional notion, which allows site division into various work areas. This
function is mostly informative. A department can be chosen as a selection criterion to display
and print reports.
Examples
Administration, Top Management
Fields
Fields
Create a group of badges: Click for creating a series of badges (in another new window, see
Group of Badges paragraph).
Advanced settings: Displays advanced features related to biometric readers.
Code: Enter directly the card code. Generally, this code is written on the badge as a sequence
of 8 characters using numbers from 0 to 9 and letters from A to F. If the length of the
code is shorter than 8 characters the system will complement it by adding zeros at the
beginning of the code. A default badge code can be automatically inserted at the beginning of
all badge codes with the Tools -Options - General screen.
Note: This code is downloaded to the controllers and saved in the application database. The
code may be read differently according to the reading technology defined in the Reader -
General tab and the Badge format defined through the Reader - Miscellaneous/Badge format
tab.
Get from card: Click for opening the following
screen in order to get the code by reading the
card:
To get the card code from a regular reader,
pass the card on one of these readers: when
the card code appears on the window, select it
and press OK.
To get the card code from a biometric reader,
select the relevant reader in the lower get
card code from bio reader window, press the
button right to this list and pass the card to the
selected reader: when the card code appears
on the window, select it and press OK.
Type: Select the badge technology from the displayed list (Magnetic, Wiegand, etc.).
Note: Reading technology is defined in the Technology field in the Parameter - Controller -
Reader - General screen. Only badges data compatible with the selected technology will be
downloaded to the readers.
Note: Make sure that the system has calculated the Bio ID and that is not 0. Cards that were
defined prior to the creation of the first biometric reader, will have Bio ID = 0. For these cards,
calculation of the corresponding Bio Template ID will be done automatically only when the card
owners will enroll the finger. After a biometric reader definition, each new badge will receive
automatically a Bio ID code, which is displayed in the Bio template ID field after saving. A
manual calculating is also possible by selecting the "Advance settings" box and pressing
Calculate 1 (to re-calculate the selected badge) or Calculate all (for all badges in the
database, including those that are not 0). If the field remains empty or null it means that the
system cannot calculate the Bio ID and it has to be entered manually or be read directly from
the biometric reader. To obtain the code from the card itself, use the Get Bio ID window field.
There you need to select the reader from the list, click on the ID button, and pass the badge
at the biometric reader.
Owner: Select to assign a badge to an employee; when an attributed code is selected, the
name and surname of the badge holder appear in this field. The field remains empty if the code
entered is not attributed. Click on the [] button to display the employees screen.
Description: Describe the new data entry
Get Bio ID: Visible by checking the Advanced settings box. To enroll directly the Bio ID
from a biometric reader (BioProx or BioFlex), select the relevant enrollment reader from the
list, click on the ID button and then pass the badge at the selected biometric reader. The Bio
ID should appear on the Bio template ID field.
Examples:
In the Code field type The system displays all the card codes attributed
32 Beginning with 32
_ _ _ _32_ _ Which contain the characters "32" at the 5th and 6th position
Note:
% will replace several characters
_ (underscore) will replace one single character
Fields
First card code: Type the 8-character code assigned to the first badge
Note: A beginning card code common to all badges can be set in the Tools - Options -
General screen.
Quantity: Type or select the number of badges to create; the list has been provided for
information. The maximum number of badges depends on the plug limitation.
Type: Choose the badge technology from the displayed list (Magnetic, Wiegand, etc.).
Note: The choice of reading technology will enable selective data download to the readers.
Only data compatible with the selected technology will be downloaded to the readers.
Position to increment (between 0 and 8): Define the position of the character to increment in
the 8-character sequence making up the code. This allows keeping a constant group of
characters as code endings. To use this function, it is necessary that only decimal
numbers compose the beginning of the code, till the position to increment.
Example
Create also cardholders: Create simultaneously a group of badges and their associated
badge holders, which will have:
Basic parameters: Valid employee parameters to whom the Anytime Anywhere access
group is attributed
Set parameters same as: Specify the name of the badge holder whose parameters will
serve as reference for the new badges
Fields
First card code: Type the 8-character code assigned to the first badge
Quantity: Type or select the number of badges to delete; the list has been provided for
information. The maximum number of badges depends on the controller and plug limitation.
Position to increment (between 0 and 8): Define the position of the character to increment in
the 8-character sequence making up the code. This allows keeping a constant group of
characters as code endings. To use this function, it is necessary that only decimal
numbers compose the beginning of the code, till the position to increment.
Example
Remove also cardholders: Delete simultaneously a group of badges and their corresponding
badge holders
Remove all non allocated badges: Delete all cards that are not allocated anymore, i.e.
temporary cards
Remove all deleted cardholders: Select to remove all deleted cardholders from the database
Quick definition
The family name is the only obligatory field for creating a new badge. Nevertheless, in order to
grant access, the field Badge is necessary. The Anytime Anywhere access group is
associated by default to the new cardholder.
Note: If the validation date chosen belongs to the past, the Validation box will be checked
automatically. Beyond the specified validity date, the badge will automatically become invalid.
Every 30 minutes, at xx:15 and xx:45, the program checks if new cardholders need validating
or invalidating, in which case the corresponding cardholders definitions are sent to the
controllers. The frequency of this checking may be modified through the Tools - Options -
Communication screen (default: 30 minutes).
Set as default: By checking this box, the badge holder selected serves as a reference. His
parameters are automatically copied as default parameters for newly created badge holders.
This function saves the trouble of having to define the same parameters for each cardholder
that will be created in the future.
1 2 3 4 5 Day
23:00 00:45
John SMITH John SMITH
passes his cannot
badge access
for the last time anymore
A cardholder that passed his badge the day 1' (at any hour!) will have access on days 2', 3'
and 4'. If he did not pass his badge at a reader of the system during these 3 days, the system
will invalidate automatically his badge on day 5' at 00:45 a.m.
Operating Mode :
Exit the application and look for the ini file at the main application folder.
Open it with Notepad and look for the following entry:
AutomaticInhibition = 0
If this line does not exist, run the application, go to Tools - Options and click OK. This
operation rebuilds the ini file and inserts all the possible entries according to the latest
application version.
Set the value according to the required days number before inhibition.
Example, to inhibit all the cardholders that did not pass their badge during 3 days, set:
AutomaticInhibition = 3
Note :
If the PC is turned off all the nights, the inhibition command will not be able to be sent to the
readers at 00:45 a.m. This function works only if the application is runing at that time.
Operating Mode
The design tab is based on a professional tool of Active Report . In this manual we will not
cover the large variety of options but we only give some basic instruction and tips:
Moving selected fields: Select an existing field from the Detail window and drag and
drop to the required position of the layout.
Add a new field: Select the field type from the toolbar on the left and drop it in the layout.
Add a field from the cardholder database: Click the View - Explorer menu. Two
windows will appear on the left. On the lower one, click the refresh icon. All the fields of
the cardholder screen will appear. Drag any field and drop it in the layout area.
Change the background: Select the current background. On the Property ToolBox, go
to the Picture field, click on the [] button and browse your PC for any graphic file.
Change the text in a label/text box: Select the field and edit the text on the Property
ToolBox window, in Caption (for a label) or Text (for a text box). Dont change Name.
Save changes to the current layout: Click on the Preview tab.
All editing changes are saved into the default layout when the Preview tab is displayed. The
default layout is called _bp.rpx and is located on the application folder.
Different customized badge layouts can be saved on the \Reports\BP folder under the
application folder with RPX format. Saved layouts will appear in a combo box in the All
cardholders - General screen, left to the badge printing button (the former layout is
automatically saved as layout1 ). This leads to create and print different format badges into
a same database. It is possible to save many layouts as required and for printing a specific
badge layout to a cardholder, it just needs to select it on the layout list.
! Warnings:
Do not delete the default photo (cardholder image) field from any layout.
Do not delete the icon ADO from any layout.
Do not move, close or resize the Property ToolBox window.
If by mistake you have done any of the above action, you may need to go back to the
default layout: Exit the All cardholders screen, go to the application folder and delete the
_bp.rpx file.
Operating Mode
Once a biometric reader is configured for use as an Enrollment reader, it is possible to enroll
fingerprints for existing users. The information created during the enrollment process is stored
as a Template. Template contains one fingerprint, its associated card code and other related
data. Each template is save twice: in the PRONET PLUS database, as well as in all the active
biometric readers.
In the current screen, select the relevant biometric reader from the combo list (This list
displays only readers defined as Enrollment readers).
Press the Enroll button for fingerprint enrollment, then follow the instructions on the
screen. The message PLACE your finger on the sensor should appear.
Put the finger on the reader until the graphical image of the fingerprint appears on the
screen and the message changes to Remove finger. Ready to save.
Press the Save button for saving this fingerprint and for downloading it to all the active
biometric readers.
Fields
Fields
Fields
In addition to these four labels, users can add an unlimited number of new fields through the
Parameter - Customized fields screen. The fields types can be defined as Text, Date,
Boolean or Number. Text and Number type fields can have a combo box for selecting
customized options. The list values should be typed, separated by <;> in the appropriate field
of the Customized fields screen.
Note: Once saved, the relevant field can be seen at the All cardholders - Customized screen.
After saving a new field, it is NOT possible to rename it or change its type. However, it is
possible to delete it.
Example
This enables the secretary at the entrance of the building, or the guard, to create a temporary
badge for visitors without having the need to access the main employees database.
Note: This screen is identical to the Parameter - All Cardholders screen except that the
Type field is set to visitor and does not appear on the screen.
When a cardholder is defined as Visitor, the new tab Visitor is added, to specify visit
information.
Fields
What to do:
Check that the plug allows the multi-company application: Open the Help - About
PRONET PLUS screen and check in the plug definition that the pug contains the letter
M.
Activate the multi-company capability and display the fields related to the multi-company
application: Select the Multi-company function in the Tools - Options -Server screen.
Create the different companies sharing the application: A user should create the
companies in the "Parameter - Company" screen.
Allocate a user within each company: Create in the "Parameter - User" screen each user
who will be responsible for system set up definitions for his own company.
Modify the default name, password and company of the default user: Change it in the
"Parameter - User" and "Parameter - Company" screens and remember it.
Each user sets up the system parameters for his own company.
Example
Default User
By default, the system defines a user (name: ACTEC, password: ACTEC) for the default
company called "Building Management".
Displaying the current user name
The name and the company of the current user are always displayed in a white box at the far
right of the tool bar.
Multi-site application
The multi-company application can be used for multi-site installations. The central database
encompasses the information about all the companies. The multi-site manager will receive a
user name and password for each site. He will be able to enter the different sites and control
the events within each entity.
3.10.2. Company
The "Company" screen is used to create new companies in a multi-company application.
Fields
Name: Name the new company
Description: Describe the new item
3.10.3. Super-User
The super-user is a special user whose functions are:
Creation and deletion of new companies sharing the application
Allocation of a first user for each new each entity
Decision on who the other super-user(s) will be
Creation and restoration of database and journal
One super-user is required for the default company and optional for the other entities. The
default user is defined as default super-user by the system. The default super-user cannot be
erased; nevertheless his name can be modified. All further super-users created can be
modified and erased.
Only a super-user can delete companies, all entities but his company or the default one. The
possibility to create and delete a company database will not even appear on the screen of a
user.
A user is defined as a super-user by selecting the option in the "Parameter - User" screen.
3.10.4.2. Exceptions
Cross companies
If an employee from Company A presents his badge to a reader from Company B, the access
denial message will be notified to both companies.
Shared Items
The shared items and its definition are available to all in a read only mode. Only the company
that owns the item can modify it.
A. Shared controller networks
By default, the default network (Network 1 on COM 1) is shared. The sharing possibility can be
manually removed.
B. Shared readers
Example: Company A owns the main entrance reader. It lets Company B use that reader.
A company that owns a reader can share it, by checking the corresponding box in the
"Parameter - Reader - General" screen. By doing so, the ground is set to allow all employees
all companies to use the reader. The system will automatically insert this reader into the
"Anytime - Anywhere" default access group of all companies and update the controllers
correspondingly. From now on, all companies will be able to select the shared reader for any
access group manually created.
The weekly program associated should either be:
"Always", or whatever modified name it has, in which case the company it originates
from is of no significance - recommended to keep full control of the access.
Any other weekly program of the company that has shared the reader.
C. Shared computer
A computer can be shared between different companies. The "Log Off" function can be useful
in this case.
D. Shared icons
By default, icons created by a company can be seen and used by all companies. Only the
company that has created the icons can modify them.
Examples
The site manager has access to all the information
The parking lot attendant can only modify information regarding parking and view user
details
The secretary at the entrance of the building can only create visitors badges
Once authorization levels have been created (through the following screen), they must be
attributed to users in the Parameter - User screen.
Fields
Screen status: V or X or R
The application allows differentiating within a head chapter, the screens that are
accessible, restricted and forbidden. Viewing status can be modified by clicking
successively on the sign to the left of the screen definition:
Select V, to define accessible screen (read, write and delete)
Select X, to define forbidden screen
Select R, to define restricted screen (read only, without modification)
By changing the status of the head chapter, it applies automatically the same status to all
sub-menus that it contains. For example, if access to a head chapter is X to a group of
users, access to all sub-menus will automatically be X. But, the status of sub-menus can
be changed individually.
Fields
The graphical functions of the PRONET PLUS software integrate the dynamic display of inputs
on installation maps.
Define icons (Event-Handling - Icon screen), certain icons are defined by default
Link the icons to the inputs (Parameter - Controller - Input screen)
Define site maps (Event-Handling - Maps screen)
Position the inputs on the maps (Event-Handling - Position screen)
Display the final status in the Event-Handling Active alarms screen
4.1. Icon
Icons are graphical symbols, attributed to input, output, map, process or action. They will
positioned on maps and will be used dynamically in the Event-handling Active Alarms
screen.
Icons of controllers inputs and outputs are created by default.
Basic graphical symbols are supplied in the directory:
C:\Program Files\Amadeus5\Media\Icons
Other icons can be added by specifying their name, description and location on the disc. They
are automatically stored with all the icons in the directory mentioned above.
Fields
4.2. Map
The Maps screen allows the integration of maps into the software. In order to use the Active
Alarms function, inputs must be positioned on maps.
It is advised to store all maps in the following directory:
C:\Program Files\Amadeus5\Media\Maps
Fields
Field
Fields
Positioning
Modifying the input position on the map can be done using a mouse: select the object,
maintain the left mouse button depressed and move the mouse towards the new position.
Example
Grouping all the protection system inputs of a room, such as movement detectors or windows
and doors opening devices. A single command will allow render the group status from active
by night to normal mode by day.
Fields
Fields
View:
Check V button to display the inputs list included in the input group
Check X button to display the inputs list excluded from the input group
Controllers list: Select the required controllers. Inactive controllers are represented in grey.
First column of the table: V or X
Select V to include the input in the input group
Select X to exclude the input in the input group
By default, all the inputs from the list are excluded from the input group.
Input: List of all inputs of the selected controllers
Example
Activating of an output group (for example all the door relays) upon a fire alarm.
Fields
4.6. Action
All actions available in the application are listed in the Event handling - Action screen. They
can be sequenced within a process and incorporated into global reflexes. The actions are
created in this screen; they can be activated via:
Icons positioned on maps
Processes encompassing these actions
Global reflexes encompassing these processes
New and personalized graphical interfaces can be created using the actions by linking several
menus and sub-menus through actions icons. When specific users log in, the new interface will
appear while the software application stays hidden in the background. This is achieved by
opening the Event Handling - Active Alarm screen on the login of a specific user with a
selected default map.
Operating Mode
Select a new background / new map (Event Handling Map screen)
Create new actions (Event Handling Action screen)
Place the actions icons on the new interface (Event Handling Position screen)
Visualise the new interface (Event Handling Active Alarms screen)
Fields
Make it a process: Click on this button to create directly a process beholding this single
action. The action needs to be saved prior to the process creation.
Test: Click on this button to test the selected action.
Name: Name the new action
Description: Describe the new data entry
Icon: Choose the icon representing the action in the list, or click on the [] button to create a
new one.
Action type: Select the action type from the list
Other Parameters: Complete the supplementary fields depending on the type of action
selected (see the Types of actions with parameters table).
4.7. Process
A process is a set of actions used to define global reflexes. In this screen the different actions
are selected and organized; their activation depends on the activation of the global reflexes
they are part of.
Fields
Examples
Count the number of persons in a room (so as not to leave a room empty, to signal
excess of maximum capacity, to switch office lights off when all the occupants have left,
to activate an alarm system when all the employees have left the building, etc.).
Decrement the number of entries of a membership club card after each passage and
refuse access if credit is null.
Check the filling up of a parking zone or cinema and refuse access to a full zone.
Operating Mode
Create a counter
Create an action/process incrementing the counter
Create an action/process decrementing the counter
Create a global reflex determining which event increments the counter
Create a global reflex determining which event decrements the counter
Warning: Conditions linked to a counter may also trigger some processes: be aware not to
create a logical loop: a process which trigger a counter which trigger under certain conditions
the same process.
Fields
Name: Name the new counter
Description: Describe the new data entry
Min: Enter the minimum value of the counter
Max: Enter the maximum value of the counter
Actual value: Enter the actual value of the counter; this value is automatically modified by the
system, when the counter is incremented or decremented.
Condition 1 & Condition 2: Define the processes to trigger following the actual counter value
True condition: Select the condition to apply from the displayed list:
Actual value <, >, =, or not equal Min value
Actual value <, >, =, or not equal Max value
Min value < Actual value < Max value
Actual value = Min value +1
Actual value = Max value -1
Process to activate when the condition becomes true: Choose a process from the list
or create a new process using the [] button.
Note: The both conditions are independent.
Examples
Print instructions
Sound a vocal file
Display the activation of a camera in the area concerned
Being informed of the arrival of a specific person
Send a message to an employee when he badges
Activation or deactivation of alarms
Switching on the air conditioning in the office of the employee that badges at the entrance
Light a red light if a parking is full
Fields
Fields
Event: The screen is modified according to the type of event selected, displaying the
appropriate number of parameters in each case.
Event type: Select the suitable event from the list (Access granted or denied at specific
reader for a specific cardholder, Start or end of alarm for digital inputs, Unknown or non-
allocated badge at specific reader, Scheduler, etc.). The table hereafter sums up all the
event types of with the parameters.
Other Parameters: Complete the supplementary fields depending on the type of event
selected (see the Types of events with parameters table).
Note: For each parameter, the <Any> item is used for selecting all the elements of the
list.
Process: From the list, select the process to activate following the occurrence of an event, or
create a new process using the [] button.
Time out: Maximum delay, between the time of the event (date and hour registered in the
controller) and the time of the PC when it receives the event, beyond which the process is not
carried out and the global reflex associated will not be performed (Expressed in second,
maximum of 9 hours, default value = 3600 sec).
A global reflex is performed only if the delay between the recording of an event by the
controller and the processing of the data by the PC is inferior or equal to this time out delay.
Example
A global reflex has been defined as follows: An input under alarm triggers the activation of a
group of relays. At 10:00 AM, the input detects an alarm but the controller is off-line (no
communication with the computer). At 12:00 AM, the communication is back, and the computer
receives the alarm event. Should the global reflex be triggered two hours after the event has
occurred? Therefore, if the time out is 3600 sec (1 hour) the global reflex will not be triggered.
Fields
Fields
View:
Check V button to display the inputs list included in the event handling program
Check X button to display the inputs list excluded from the event handling program
Option selection: View inputs / View group of inputs: This selection is visible after selecting
Alarm definition for group of input option in the Tools - Options - General screen.
View inputs: Click on this button to display a list of the individual inputs
View group of inputs: Click on this button for displaying the input group list with their
weekly program and setting a weekly program for each input group. This saves
allocating a weekly program to each individual input. In case of a conflict, the
definition of the individual input always gets the higher priority.
Controllers list: Select the required controllers. Inactive controllers are represented in grey
First column of the table: V or X
Select V to include the input in the event handling program
Select X to exclude the input from the event handling program
By default, all the inputs from the list are excluded from the event handling program.
Input: List of all inputs of the selected controllers
Weekly program: Select the weekly program associated to the input.
Note: An alarm input is only armed during allowed periods (Green periods) of the Daily
Programs defined by the selected weekly program.
Instructions: Enter the instruction to display in the Active Alarms screen when the
corresponding alarm is raised.
Button [] (on the input line): Click on this button to display the properties screen of the
selected alarm.
Fields
Table analysis
View:
Check V button to display the global reflexes list included in the event handling program
Check X button to display the global reflexes list excluded from the event handling
program
First column of the table: V or X
Select V to include the global reflex in the event handling program
Select X to exclude the global reflex from the event handling program
By default, all the global reflexes are included in the event handling program.
Name: Name of the global reflex
Event: Event associated with the global reflex, i.e. the event that will trigger the process
defined in the reflex.
Process: Process associated with the reflex, i.e. the process to be executed when the event is
occurred.
Button [] (on the line of the reflex): Click on this button to display the general screen of the
selected global reflex for creating, consulting or modifying data.
Button [] (outside the table): Click on this button to display the general screen of the global
reflexes, even if no item is selected.
4 states or supervised input: in addition to the two basic states of the sensor/detector (open
or closed), the input may detect two supplementary states which correspond to the status of
the line used to connect the sensor/detector to the input: line cut or line short. Note that the
alarm linked to this two supplementary status, line cut or short, is always armed, i.e. it is not
possible to attribute to them a weekly program. The input type (digital or digital 4 states)
must be indicated in the input definition screen.
Consult the controller documentation to check which type of inputs is available in the controller
and how to connect a 4 states input.
Input status or input physical status: the physical status of the sensor/detector connected to
the input: either open or close.
Input normal status: The normally status of an input, either NO for Normally Open or NC
for Normally Closed, is the status, open or close, into which the sensor/detector connected to
this input is not under alarm. This normal status must be indicated in the input definition screen
(see Controller - Input paragraph).
Input off/on or input logical status: An input is off when it is in its normal status and on
when it is not in its normal status. It represents the logical status of the input. From the Input
definition screen, two icons may be defined (and positioned on a map, as described in the
Position paragraph) to represent the logical status of the input, either on or off.
Armed/disarmed input: To each input may be attributed a Weekly Program (from the Input
definition screen): the input is armed during the green periods defined in the Weekly Program
and disarmed during the red periods (See Time zone chapter for details).
Activated input: an input is activated when the following conditions are true: it is armed and
its status is on, i.e. it is under alarm during green periods of its Weekly program.
Outputs concepts:
Output: a controller output point which is in fact the output contact of a controller relay. In
general, controllers have by default 4 relays and may be extended to 16 or more. Such relay
gives a dry contact, and may be represented by an electrical switch which can be either open
or close. When the relay is closed, the device (door, siren, etc.) which is connected to the relay
is activated.
Output status: the status of the relay, i.e. open (or activated or on) or close (or deactivated or
off). As for an input, two icons may be defined to represent the output status. (in the Output
definition screen)
The Active alarms screen is accessible from the Main menu tool bar. It is divided into three
tabs:
Map tab: allows to display the site maps,
Input status tab: allows to display the different status of the inputs,
Output status tab: allows to display the different status of the outputs.
Toolbar
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Alarm Table: The window below the toolbar shows the actual alarms status (active,
acknowledged or confirmed):
Name: Name of the alarm input. The icon before the name shows the alarm status:
Active (red icon)
Acknowledged (green icon)
Confirmed (the alarm disappear)
Date: Date and time of the alarm
Priority: Alarm priority (defined in the Event-Handling Program - Alarm Properties screen)
Alarm type: Start of alarm, line cut or line short
Buttons [c] & [d]: Click on the direction arrows to select the requested alarm
Instruction: Instruction which appears when the alarm is raised (defined in the Event-
Handling Program - Alarm Properties screen).
On the site map: Point the mouse on an icon in the map, click on the right button and choose
among the following functions:
Input icons
Acknowledge (when under alarm)
Confirm (when under alarm)
Open input properties
Return to normal mode
Input deactivation
Relay icons
Open relays properties
Return to normal mode
Deactivate relay continuously (constant off)
Activate relay continuously (constant on)
Activate relay during, specify the number of seconds
Process icons
Execute process
Open process properties
Action icons
Execute action
Open action properties
Note: Only the actions allowed for the user will appear.
Automatic refresh
The icons status can be automatically updated by selecting the Auto-refresh Input/Output
status option in the Tools - Options - Server screen. Alternatively, when the Auto Refresh is
off, a manual refresh button can be used on the top bar.
Dynamic map management
In case of several maps, the displayed map is the one encompassing the activated inputs. If no
alarm is signalled, the default map is displayed. If several alarms are activated, the map
containing the most recent alarm raised will be displayed. If the Event Handling - Active
Alarms screen is already open and a new alarm belonging to the displayed map is triggered,
this map is dynamically updated. Actions and process can be directly executed by right clicking
on their icons. It is possible to swap from map to map by selecting the required map either
using the map selection drop down menu or by clicking on the appropriate icons, if such icon
has been previously positioned.
How Alarms are shown
If the show all inputs button is not selected, the screen shows only the logical status of
activated inputs, i.e. the armed inputs actually on (active alarms). The icon appears
immediately when the alarm is detected, without the need of using the refresh button. The
icon of an activated input stays in the map until the operator acknowledges and confirms it.
If the show all inputs button is selected, the screen shows the logical status of all the
inputs defined in the Position screen.
The dynamic swap of icons allows for visual follow-up of input and output status: activation or
deactivation of alarm points, door open or close and relays supervision.
Example: If a door alarm is detected, an icon will show an open door. If the door is closed, the
icon will be updated to a closed door.
When an alarm is raised the system reacts
Log display: alarm displayed in red
Journal: event is recorded
Navigation bar: increase in the number of alarms raised
Active Alarms screen: the icon connected to the alarm appears on the site map displayed
Active Alarms screen: mention of the name of the input activated and the date of the
event in the top table
Active Alarms screen: instructions related to the alarm input are displayed in the
Instruction window.
When several alarms are detected, the last alarm is displayed in the table at the top of the
Active Alarms screen. By clicking on an alarm icon, the cursor automatically moves towards
the corresponding row. The instructions displayed correspond to the alarm selected. Note that
the order of the active alarm table can be manually sorted, by clicking on the column header.
Such a sort cancel the default sort (by date), and therefore the last alarm may appear in the
middle of the list.
Table analysis
Controllers list: Select the required controllers. Inactive controllers are represented in grey
Name: Input name
Controller: Controller name that the input belongs to
Num: Input number in the controller.
Type: Mention if the input type is Digital, Digital 4 states or Analog.
NO/NC: Input normal status, i.e. normally open (NO), normally closed (NC) or State 1 to 4.
Physical status: Open, Close, Line short or Line cut. During reading time or communication
problems with the controller, a ? mark is displayed to show that the status is unknown.
Logical status: On, Off, Line short or Line cut (or ? if the status is unknown).
Armed: The arm status switches between:
(Red icon) Armed: The current time falls within the activation boundaries of the input
weekly program (green periods).
(Black icon) Not now: The current time falls outside the activation boundaries of the
input weekly program (red periods).
Disarmed: The input is not included within the Event Handling Program.
The system automatically goes from Not now to Armed, and vice versa, according to time
zones.
Active alarm: Coloured icons signal the alarm status (active, acknowledge and confirmed) in
the table as well as in the tool bar
(Red icon) Active: Active alarm
(Green icon) Acknowledge: Acknowledge alarm
No icon: Not in alarm or alarm confirmed
Latest action: Shows if the normal situation has not temporarily been affected manually or by
the activation of an action, a process or a global reflex.
Manual action
Point the mouse on an input name, click on the right button and choose among the following
functions:
Acknowledge (when under alarm)
Confirm (when under alarm)
Open input properties
Return to normal mode
Input deactivation
Sorting out information
The information in the table can be sorted out. Each column can serve as a sorting criterion.
To organize information in an increasing order, click on the column header. To sort the
information in a decreasing order, click again on the column header.
Alarm prevention
To prevent the alarm apparition, resulting from input activation, choose one of the following
methods:
Delete the input from the input list (in Controller - Input screen).
In the Event-Handling Program - Alarms screen, select X to exclude the input from the
event-handling program.
In the Event-Handling Program - Alarms screen, attribute the WP Never weekly
program to the input.
From the Active Alarms - Map screen or from the Active Alarms - Input Status
screen, right click on the input and select Input deactivation.
Example
Table analysis
Controllers list: Select the required controllers. Inactive controllers are represented in grey
Name: Relay name
Controller: Controller name that the relay belongs to
Num: Output number in the controller.
Physical status: Open or Close. During reading time or communication problems with the
controller, a ? mark is displayed to show that the status is unknown.
Time activation: This column shows if a Weekly Program has been attributed to the relay:
V ON by weekly program: The relay is activated because a weekly program has been
attributed and the current time falls within the activation boundaries of the weekly
program (green periods). The relay is automatically activated according to time zones.
X OFF by weekly program: The relay is deactivated because a weekly program has
been attributed and the current time falls outside the activation boundaries of the weekly
program (red periods). The relay is automatically released according to time zones.
No text: No weekly program has been attributed to the relay.
Note: The WP Always weekly program permits to trigger incessantly a relay while the WP
Never weekly program ensues in a constant deactivation.
Latest action: Shows if the normal situation has not temporarily been affected manually or by
the activation of an action, a process or a global reflex.
Manual action
Point the mouse on an output name, click on the right button and choose among the following
functions:
Open relays properties
Return to normal mode: To cancel all actions described below.
Deactivate relay continuously (Constant OFF): To close a door permanently for example
Activate relay continuously (Constant ON): To open a door permanently for example
Activate relay during: To switch on / off an indication light, during a defined delay for
example. Specify the number of seconds (between 1 to 120 sec.).
Sorting out information
The information in the table can be sorted out. Each column can serve as a sorting criterion.
To organize information in an increasing order, click on the column header. To sort the
information in a decreasing order, click again on the column header.
5. Modules MENU
PRONET PLUS, according to the plug used, may contain several modules which are described
in this chapter (the plug description, and therefore the installed modules, can be displayed in
the Help - About PRONET PLUS screen).
5.1. Parking Module
5.1.1. Parking Module - Basic Concepts
The parking module allows for access control to parking lots and for management of parking
zone fill-up, according to user groups.
The system ability to manage the parking activity is based on three concepts:
Parking lot: Physical area where cars are parked, controlled by one or several access
points (card readers). PRONET PLUS may manage one or more parking lots.
Parking users group: Any company or entity that rents or owns parking spaces. Each
cardholder of this company may belong to a parking users group.
Parking zone: A certain number of spaces allocated to a parking user group in a
specific parking lot. A defined parking zone will be only accessible by the corresponding
parking users group.
A cardholder may access a parking lot only if his parking users group has a parking zone in
this requested parking lot, and this parking zone is not full.
Zone 6
Lot C
Zone 5
Zone 2 Zone 1
(company Y) (Company X)
Lot A
Zone 3 (company X)
Lot B
Zone 4
(company Y)
: Free Space
: Occupied Space
The previous diagram (Fig. 5.1) illustrates the map of a building car park. The Company X and
the Company Y rent parking spaces in this building:
-The Company X rents 4 parking spaces in the Lot A and 2 parking spaces in the Lot B.
-The Company Y rents 3 parking spaces in the Lot A and 5 parking spaces in the Lot B.
To implement this requirement, it is necessary to create the following items:
Two parking lots: Lot A and Lot B
Two parking users groups: Company X and Company Y
Four parking zones:
o Zone 1 (4 spaces): Company X in Lot A
o Zone 2 (3 spaces): Company Y in Lot A
o Zone 3 (2 spaces): Company X in Lot B
o Zone 4 (5 spaces): Company Y in Lot B
All the cardholders of a user group are interdependent. Access to members of a user group is
contingent to the space available in the zone allocated to the group. If five employees of
Company X arrive at the same time in parking lot A, access will be granted to the first four cars
and denied to the other cars of the group.
Access permissions to a parking lot are independent of authorizations to other parking lots. An
access denial in Lot A does not prevent access in Lot B.
If all the parking spaces of a company are occupied, other cars of this company will be denied
access. Nevertheless other cars from other companies could still reach their respective zones
in the same parking lot according to their own occupancy rate.
Operating Mode
In the Modules - Parking Lot - General screen, create parking Lot A and Lot B.
In the Controller - General screen, create two controllers as parking and allocate to one
the parking Lot A and to the other, the parking Lot B.
In the Modules - Parking Users Group - General screen, create two user groups,
Company X and Company Y.
Allocate each member to his user group, by selecting from the Parking user group list
from the All Cardholders - Personal screen.
In the Modules - Parking Zone - General screen, create the 4 parking zones, by defining
the parking user group, the parking lot and the maximal number of places.
The Modules - Parking Zone - Access screen gives a list of the relevant readers. For
each parking zone, indicate which reader is used for entrance in the zone, for exit the
zone or is neutral, i.e. not used for this zone (it not modifies the places number). Specify
whether it should allow/deny access when the zone is full (for example, if it is used for
exit, exit must be granted when the zone is full).
A free space counter is linked to each parking zone. The movement of vehicles affects the
counter level. For each car that enters, the amount of space is reduced. Each time a car goes
out, the counter is incremented by one unit.
The number of space available can be computed at any time with respect to maximal parking
capacity and counter status. A zone is full when the free spaces counter indicates zero.
Fields
Data displayed
Fields
Data displayed
Fields
Fields
Fields
Duplicated items
In the list of cars currently in the parking zone, duplicated items can be exist in case of the
badge has been swiped twice at the entrance or if the same badge has been used for two cars.
To avoid such a situation, the solution consists to define the readers with the (Global, Time or
Local) Anti-Passback function.
The application provides three ways to reset the parking zone counters:
Punctually, by choosing the Reset Parking Zones menu and by answering Yes to the
question,
Daily, in automatic way, by selecting this option in the Tools - Options - Server screen
and by specifying the requested time for this operation,
Automatically, by global reflex, by creating an action with the Reset parking zones type
and by selecting which parking zone to update. Then, a global reflex may reset a specific
parking zone counter by any trigger of the system (by swiping or by changing input status).
It may reset the counter at a specific time, by choosing the Scheduler as global reflex
event type and specifying the date and hour when the parking zone needs resetting (For
more details, see the Event handling - Actions and Event handling - Global Reflex
screens).
LIFT
5.2.1. Lift Module - Basic Concepts
This function manages access to the floors served by one or several lifts. The floor buttons of a
lift are controlled by controller relays. The badge holder swipes his card through a lift reader:
according to its authorizations, one or several relays are activated which unlock the
corresponding floor buttons so that the badge holder may then press the button of the floor
requested.
A lift program defines the floors combination accessible by a group of users. This function does
not control access to the lifts, nor to the areas served by these lifts. Lift programs can be
identical for all lift readers belonging to the same controller or specific for each reader. The
later is especially useful in big installations (a controller may have up to 64 relays). In a building
shared by many companies, the lift program allows each person to select only the floors
allocated to his company.
Note: If the badge holder has not selected a floor within a specified delay, access will be
denied to all floors. This prevents unauthorized persons from using the lifts.
Example
A site consists on two buildings. The first is made up of three floors and the second is made up
of six floors. Each building has its own lift.
Three user groups are defined:
Top management can access all floors in both buildings
Technical staff can access floors 1 and 2 of the first building and floors 1, 3, 4 and 5 of the
second building
Administrative people can access floors 1 and 3 of the first building and floors 1, 3 and 6 of
the second building
6 floors
building
3 floors
building
Lift
To fill the needs of this site, three lift programs must be created with the following
authorizations:
Operating Mode
In the Controller - General screen, create two controllers as Lift, one by building.
In the Modules - Lift Program - General screen, create three lift program groups, Top
management, Technical Division and Administration, and for each group, allocate
outputs to the lifts floor buttons,
Allocate each member to his lift program group, by selecting from the Lift program list
from the All Cardholders - Personal screen.
Fields
Duration time (from 0 to 120 seconds): Delay during which the cardholder has to press the
floor button after receiving access authorization; it corresponds to the activation delay of the
relay which control the floor button selection. By default, a delay of 3 seconds is set.
Note: Alternated mode (Duration time set to 122 Sec): The relay is activated (i.e. the floor
button is available) after the first valid swipe and stays activated; the relay is only deactivated
after a valid second badge reading and stays deactivated, and so on.
Table: Relays list of the defined lift type controllers
Select V to include the relay in the lift program
Select X to exclude the relay from the lift program
By default, the relays - and thus the corresponding floors - are excluded from the program.
Fields
Fields
Start date: Specify the date and hour of the beginning of the period
End date: Specify the date and hour of the end of the period
Left window: Select the reader(s) to take into account
Right window: Select the cardholders(s) to take into account
Preview: Preview the roll call report
Example
5.4.2. Guard
A guard is an employee habilitated to perform guard tours. An employee is defined as a guard
in one of the two following screens:
"All cardholders - General" screen, by manually setting his type to "Guard"
"Guard", in which the type is automatically set to "Guard".
Fields
Fields
Fields
Data displayed
Refresh: Click on this button to update manually the guard tour information.
Refresh each: Click on this button to update automatically the guard tour information. Define
the refresh delay in Sec. before.
Currently running: List of the current guard tours with mention of the guard, which patrols and
with the date and time of the beginning of the tour. By selecting a guard, the right window
displays the selected guard tour details.
Details: Information concerning the guard tour selected in the left window, including
checkpoints name with its upper and lower time limit of arrival time. Different icons are showing
the type of arrival at each checkpoint:
: Not arrived yet
: Arrival (on time)
: Early arrival
: Late arrival
: No arrival on time (inside the limit of time)
Bottom window: Log restricted to the selected guard tour.
Note: In addition to this screen, when a guard arrives at a checkpoint (by activating an input or
by presenting a card to a checkpoint reader) two messages are displayed in the main log:
Message of activated input or badge reading event,
Message of guard tour events (arrival on time, late arrival, etc.)
Example
A guard tour has the following check point: Time: 00:10 []: 00:04 [+]: 00:05
Examples
The access of a room is forbidden; it is possible to display automatically live image of the
room, as soon as someone tries to enter.
An object was stolen; the software will allow viewing all video recordings from the relevant
camera.
Operating Mode
In the DVR screen, create the different DVR, by defining their IP address, their user
name and their password.
In the Camera screen, create all the video cameras, by defining on which DVR they are
linked and what is their no. on that DVR. In case of PTZ (Pan/Tilt/Zoom) cameras, select
one of the pre-defined positions.
To display live image from any linked cameras: Create a Display live video action, add it
to a process. Activate this process either by:
o global reflex (after start of alarm, badge presentation, etc.)
o adding this process in the toolbar
o adding the action/process icon to the active alarm map, (to enable opening the camera
view directly from the Event-Handling - Active Alarms screen).
To record video from any linked cameras: Create a Record video action, add it to a
process. It is possible to activate this process in the same way as the previous process.
To view a history video record from the log: Select a video camera from the camera list of
the Reader or the Input screen in order to link this camera with all events of that
reader/input. In the Tools - Options - Journal / log screen screen, change the log type into
Rich log. Then, in the log display, a camera icon will be displayed near each transaction
associated with this reader/input (see also the Rich Log paragraph). Each transaction on
that reader/input is automatically associated to the corresponding video recording. By right
clicking on the events with a camera icon, users can see the corresponding video record.
To view a history video record using the report wizard: Select a video camera from the
camera list of the Reader or the Input screen in order to link this camera with all events
of this reader/input. Then, through the report wizard, click Next, select "Journal Simple"
from the list of available reports and click on the View data". Events from these
readers/inputs linked are shown with a camera icon. Right clicking on these events gives
an option to view the corresponding video records.
Fields
Fields
Commands
Resume polling (shift + F8): Select this option to activate the polling
Stop polling (shift + F8): Select this function to stop polling
Keyboard Shortcut
Use the shift F8 key at any time, from any screen, to modify polling status.
Polling at start-up
By default, the system carries out a polling activity at the start of the application. This option
can be modified in the Tools - Options - Communication screen by changing the status of the
Do polling at start-up function.
6.2. Diagnose
The diagnose screen allows the visualization of the controllers status and the biometric readers
status. This screen is made up of two windows:
Left window: Controllers list / biometric readers list
Right window: Information regarding the selected controller or biometric reader
Selecting a controller or biometric reader from the left window activates the right window where
the details of the selected controller or biometric reader are displayed.
Download: Menu of the available downloads for the selected controller or biometric reader
Communication: allows to check the communication with controllers:
Check communication (All)
Check communication (selected): Select the controller(s) to check (by clicking on the
button next to the controller name)
Refresh every: For automatic checking. Select the controller(s) to check and define the
refresh delay in Sec.
Hardware: allows to check the inputs/outputs status of the controller displayed in the right
window:
Refresh status: Display before the selected controller details in the right window
Refresh every: For automatic checking. Select the controller(s) to check and define the
refresh delay in Sec.
Status for: Choose the information to display:
Controller: Press this button to display the controllers status
Biometric readers: Press this button to display the biometric readers status:
From the Download menu it may be possible to initialize one or several biometric readers
by re-sending all the database templates after deleting all the fingerprint templates from the
reader memory.
Data displayed
Left Window: The controllers / biometric readers list, is sorted by their controller network.
Controller or biometric reader communication status is graphically represented as follows:
Grey: if the controller or the biometric reader is not active, (the communication is not
monitored by the system)
Bold: if the controller or the biometric reader is active, (the communication is controlled
by the system) in which case, by clicking on the controller or biometric reader name, V
or X icon is displayed next to the name:
X: absence of communication
V (with date and hour): communication established; the controller or the biometric
reader details are displayed in the right window
Right window: Details of the controller or the biometric reader selected in the left window
Controller or Biometric reader name
Status received at: Date and hour of the event (the controller time when request was put
in can differ from time of request if internal controller clock is late)
Network type: Network name, which the selected controller or biometric reader belongs
to:
Port and address of the network: COM, TCP or Modem
Communication speed (in bauds)
Time out delay (in milliseconds)
Time out polling (in milliseconds)
Waiting delay (in milliseconds)
Controller address (from 00 to 31) or Biometric reader address
Keyboard Shortcut
Use the F8 function key at any time, to display the diagnose screen from the software main
screen.
Fields
A site is composed of three doors: Entrance Door, Office Door and R&D Door.
In a normal situation, all authorized employees can enter at the Entrance Door, the engineers
are denied access to the Office Door and some secretaries can enter at the R&D Door.
In case of emergency, even the engineers are denied access to the R&D Door.
Menu
Action:
Refresh: Click on this button to update manually the relays information.
Return to normal mode: To cancel all actions described below.
Activate relay continuously (Constant ON): Constant relay activation, for a permanent
door opening for example.
Deactivate relay continuously (Constant OFF): Constant relay deactivation, for a
permanent door closing for example.
Activate relay during: Temporary relay activation, for switching on / off an indication light,
during a defined delay for example. Specify the number of seconds (from 1 to 120 sec.).
Table analysis
Left Window: System controllers list sorted by controller network. Select the required
controllers. Inactive controllers are represented in grey.
Name: Relay name
Controller: Controller name that the relay belongs to
Num: Output number in the controller.
Physical status: Open or Close. During reading time or communication problems with the
controller, a ? mark is displayed to show that the status is unknown.
Time activation: This column shows if a Weekly Program has been attributed to the relay:
V ON by weekly program: The relay is activated because a weekly program has been
attributed and the current time falls within the activation boundaries of the weekly
program (green periods). The relay is automatically activated according to time zones.
X OFF by weekly program: The relay is deactivated because a weekly program has
been attributed and the current time falls outside the activation boundaries of the weekly
program (red periods). The relay is automatically released according to time zones.
No text: No weekly program has been attributed to the relay.
Note: The WP Always weekly program permits to trigger incessantly a relay while the WP
Never weekly program ensues in a constant deactivation.
Latest action: Shows if the normal situation has not temporarily been affected manually or by
the activation of an action, a process or a global reflex.
Command Buttons
Note: Double-Clicking on one of the icon of the screen launches the associated process
automatically.
Command Buttons
What to do:
To create a pre-defined standard journal report: press the Simple reports button.
To create a new report: select the Create a new report icon from the list and press the
Next button.
To print an existing report: select it from the list and click on Print button
To edit or export an existing report: select it from the list and click on Preview button
To modify an existing report: select it from the list and click on Next button
Fields
Toolbar Buttons
Operating Mode
The Design tab is based on a professional tool of Active Report . In this manual we will not
cover the large variety of options but we only give some basic instruction and tips:
Moving selected fields: Select an existing field and drag and drop to the required
position in the window.
Lengthen or shorten the space allocated to a field: Select an existing field and drag
the blue squares around the field to resize it.
Delete a field: Select an existing field and delete it.
Change the text in a label/text box: Select the field and edit the text on the Property
ToolBox window, in Caption (for a label) or Text (for a text box). Dont change Name.
Change the font: Select an existing field and change the font on the Property ToolBox
window, in the Font field.
Add a new field or a picture: Select the field type from the toolbar on the left and drop it
in the layout. If it is a picture field, go to the Picture field of the Property ToolBox, click
on the [] button and browse your PC for any graphic file.
Change the Report Header background: Select the Report Header window and change
in the Property ToolBox window, the BackColor field and set the BackStyle field to 1.
Save all changes: Select the File/Save menu and save the report on the Reports
folder under the application folder with RPX format.
Data displayed
Select the report data to display: PRONET PLUS allow the choice of the journal (period) of
the report:
From current journal (by default)
From another journal (with Access database ONLY): Select any other journal of the
system by using the [] button, and specify its name and its directory.
View data: Click on this button to preview the content of the data; click again on the View
data button to quit this mode.
Previous: Click on this button to return at the previous step of the report wizard.
Next: Click on this button to go to the next step of the report wizard.
Exit: Click on this button to close the report wizard and go back to the main screen.
What to do:
To display the available data sources of a report type: double-click on the required report
type from the left window
To display the available fields of a data source: click on the required data source from the
left window; the list of available fields appear in the right window, some of them already
selected (in blue).
To select the required fields: click on the available fields from the right window for changing
the default selection according to your requirement
To re-order the fields as required: use the arrows button to move the fields. The View
data button may be used to preview the data of the report.
To continue the creation or the modification of a report: press the Next button to go to the
next step of the report wizard
PRONET PLUS User Manual 133
8.1.4. Report wizard - Data Viewing
Open the Report Wizard, click Next, select "Journal Simple" from the list of available reports
and click on the View data".
This screen allows previewing the content of the current report data at the different steps of the
report wizard. Clicking on the View data button opens it.
Data displayed
Date, Transaction, etc.: Data fields that will be printed in the final report. The report data are
discribed below, row by row.
Icon : A video recording is linked to this event. A context menu is displayed by clicking
right on it, proposing to launch the video record linked to the corrsponding event (for use with
the Video Module ONLY).
Command Buttons
Buttons [e] & [f]: Click on these buttons to skip from one record to the next.
Buttons [e] & [f]: Click on these buttons to select the first or the last record.
View data: Click on this button to exit the screen and return to the report wizard.
Exit: Click on this button to close the report wizard and go back to the main screen.
Data displayed
What to do:
If filter is not required, press the Next button to go to the next step of the report wizard.
To keep into the report only specific data: select from the left window the fields to which the
data belong in order to display in the right window the associated filters:
If the selected field has a date format, use the filters: From, To, In the last X Months,
In the last X Days for limiting the report to a specific period.
If the selected field has a number format (i.e. Personal crisis level), use the filters:
Greater than, Smaller than, Equal to for limiting the report to one or several specific
values.
If the selected field has a Boolean format (i.e. No access during holidays), use the
filters: Yes / true, No / False for limiting the report to a specific answer.
If the selected field has a text format (i.e. Full name), unselect the All option and then,
select the data which must remain in the rapport. The Select all, Select none and
Invert buttons may help the selection. The <NULL> selection of the selected field
allows to leave in the report only the records for which this field is empty.
To preview the data of the report: press the View data button (see the Report wizard -
Data Viewing paragraph).
When only the data requested are filtered: press the Next button to go to the next step of
the report wizard.
Data displayed
What to do:
To name the report: type the name in the Save report as field. This name will appear in
the available reports list, in the Report wizard - Step 1 / 4: Report Selection screen and
then, it could be opened easily.
If sorting the report is not required: press the Finish button to save and preview the
report, as it will be printed (see the Report wizard - Step 1 / 4 - Preview paragraph).
To sort or group the data into the report: double-click on fields from the left window for data
sorting or from the right window for data grouping.
To preview the data of the report: press the View data button (see the Report wizard -
Data Viewing paragraph).
When the data are sorted or/and grouped: press the Finish button to save and preview
the report, as it will be printed (see the Report wizard - Step 1 / 4 - Preview paragraph).
To print directly the report: select the Print the report option and press the Finish button.
To modify the structure of the report: select the Design the report option and press the
Finish button (see the Report wizard - Step 1 / 4 Design paragraph).
The extension of the file is mdb (Access database only). By default, the files are saved in the
directory: C\ProgramFiles\Amadeus5\Backup.
The default destination can be modified in the Tools - Options - Files Location screen.
Fields
Look in: Select the folder where is located the required database. By default, the selected
folder is: C:\ProgramFiles\Amadeus5\Backup. This default destination can be changed in the
Tools - Options - Files Location screen
File name: Enter the filename containing the database
Files of type: Select the file type
Database files (*.mdb): Default extension for Access database
Database files (*.bak): Default extension for SQL database
All files (*.*): Ability to open a database created by other applications
Open as read-only: Check this box if the database is loaded for consultation only.
The system displays in a message (see below) the filename, which contains the former journal.
The system automatically names the saving files with the current time and date.
The extension of the file is mdb (Access database only). By default, the files are saved in the
directory: C\ProgramFiles\Amadeus5\Backup.
The default destination can be modified in the Tools - Options - Files Location screen.
Fields
Save as: Accept or modify the name suggested or select an existing filename using the []
button.
Choose one of the following options:
Save all journal in as a new file (delete if exists) (default option)
Save a part of the journal and append it into the selected file
From: Specify start date and hour of journal
To: Specify end date and hour of journal
Records: Number of selected records and total records number
Delete records in the current journal: Default option
Once the saving is done, the system displays in a message (see below) the name of the saved
file.
Fields
Look in: Select the folder where is located the required journal. By default, the selected folder
is: C:\ProgramFiles\Amadeus5\Backup. This default destination can be changed in the Tools
- Options - Files Location screen
File name: Enter the filename of the journal
Files of type: Select the file type
Database files (*.mdb): Default extension for Access database
Database files (*.jrn): Default extension for SQL database
All files (*.*): Ability to open a journal created by other applications
Open as read-only: Check this box if the journal is loaded for consultation only.
Once the restoring is done, the system displays a message (see below), with the filename of
the former journal.
Operating mode
Create a DSN from the ODBC DS Wizard (consult ODBC help for further information) or
used one of the DSN created by default (HRAccess and HRExcel).
Check that the table format is compatible with PRONET PLUS or write a request to
modify it.
Define an import database profile, as described hereafter, and import the table.
In the Event Handling Action screen, create and execute the action Import
Cardholders with the selected profile.
Fields
Fields
Example
Number Last Name First Name Type Badge Technology Company Etc
201 Smith John 1 12345678 1
202 Johnson Linda 0 22334455 1
Note: In these two files, the name of the fields cannot be modified. The two first fields are
MANDATORY.
Fields
Number: Mandatory field. Use unique values (no duplications). Modifying this number after the
first import will create a new cardholder in the access control database.
Last Name: Mandatory field.
First Name: Optional field. First or last name may be recurring, but not both jointly. For
example, two John Smith cannot be created.
Type: Optional numerical field (0-Visitor, 1-Employee, 2-Guard, 3-Deleted).
Badge: Optional alphanumerical field. Up to 8-digit code, authorized digits: 0 to 9 and A to F.
Technology: Optional numerical field (1-Magnetic, 2-Bar code, 3-Wiegand, 4-Smart card 1, 5-
Smart card 2, 6-Smart card 3, 7-Touch, 8-Radio).
Company: Optional free text.
Department: Optional free text.
Office Phone: Optional free text.
Access Group: Optional free text. Use the same name as in the access control application; if
not a new access group will be created.
PIN code: Optional numerical field. Up to 4-digit number, authorized digits are 0 to 9.
To Date: Optional date field; set the same format as your Windows regional settings.
Validated: Optional numerical field (0-Not validated, 1-Validated)
Street: Optional free text.
City: Optional free text.
ZIP: Optional free text.
Personal Phone: Optional free text.
Description: Optional free text.
Car Number: Optional free text.
ID: Optional free text.
Supervisor: Optional numerical field (0-Supervisor, 1-Not supervisor).
Label 1 to 4: Optional free text.
PRONET PLUS User Manual 145
Tips & Notes
This example explains how to import cardholders from a database that has a different structure
(different fields name, etc.):
1. Create a simple database:
Create an empty database under MS Access and save it under db1.mdb
Create a table with 4 columns and name each column (ex. Index, First, Last, Badge)
Save the table with a significant name as users
Enter at least 2 data lines for 2 cardholders (for card codes keep 8 digits)
Save and close this database
SELECT [Index] AS [Number], [Last] AS [Last Name], [First] AS [First Name], Badge
FROM users
Save and click on the Connection test button; the Database connection successful
message must be displayed. By doing this the application confirms both the connection to
the external DB and also the query syntax.
3. Automatic import:
Now, the external database is connected. It just needs to create an Import Cardholders action
with the selected profile and create the associated process and global reflex and then the
import can be done automatically, triggered either by an event (input alarm, card pass, etc.) or
at a predefined schedule.
Fields
Fields
8.11.3. Communication
Default communication parameters are defined in this tab. This tab will NOT be displayed if
the application runs as a Workstation.
Fields
Fields
Fields
Fields
Badge:
Default badge technology: Each
site works generally with a main
badge technology; the system
creates new badges using the
technology, which is selected here,
without having to specify the
technology used at each badge
creating.
Default Badge Code: Type a
beginning card code common to all
badges, if needed; this is useful
when the site code is not written
on the badges.
Main screen toolbar: A customized toolbar gives added flexibility to the system:
Save user customized toolbar: Check this box for
keeping the customized toolbars after restarting the
application; if this box is unchecked, all customized
toolbars will be lost after closing the application.
Customize main screen toolbars: Click on this
button to display the customize screen here opposite
in order to create or modify toolbars. For more details,
see the Personalized Navigation Bar paragraph.
Reset toolbar to original state: Click on this button
to recover the toolbars at their original state. This
leads to delete all customized toolbars.
Fields
Fields
Data displayed
This screen provides the software version, the plug definition and
system information.
Our access control solution based on PRONET PLUS can be integrated into any SCADA
supervision application through software module, via proprietary or OPC protocol. Tags allow
on-line bi-directional communication between the installation inputs, relays, doors, all
communication transactions, on one hand, and the SCADA relays, processes activation and
screens opening, on the other hand.
OPC defines an open industry-standard interface for the data exchange between devices,
PLC's and Windows applications. It is based on OLE and ActiveX technology that provides
interoperability between different field devices, automation/control and business systems.
The PRONET PLUS: an OPC Server document is at your disposal on the PRONET PLUS
Installation CD.
Consult your reseller to integrate access control into your SCADA application.
PRONET PLUS provides the following information to OPC Client:
Communication status of controller: Com OK or Com Error
Logical status of all inputs: Open/Close depending on NO/NC, manually
deactivated or normal status, etc.
Physical status of all relays: Open/Close, open by global reflex, etc.
All PRONET PLUS events, such as:
Access: granted, denied, granted with duress code, denied too much trials
Alarm: start of immediate alarm or delayed alarm, end of alarm
Technical alarms, such as: power off, table error, etc.
Unknown badge
Operating mode
Check that the OPC module has been purchased; the letter O should appear in the
plug definition.
Select OPC Server Activation in the "Tools - Options - Server screen.
Restart the application.
Read the PRONET PLUS: an OPC Server document available on the PRONET
PLUS Installation CD.