Manual Falcon version 223 English

Falcon ver. 2.23 User Guide

Synel Industries Ltd.

This manual was issued on 2006-01-30. Catalog no. 659993 Document no. (21-9991601-7) This document has been prepared for Falcon ver. 2.23. Copyright © 1998-2006 Synel Industries Ltd. All rights reserved. Reproduction or use, without express permission of editorial or pictorial content, in any manner is prohibited. No patent liability is assumed with respect to the use of the information contained herein. While every precaution has been taken in the preparation of this manual, Synel Industries Ltd. assumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting from the use of the information contained herein. Falcon is a trademark of Synel Industries Ltd. All trade names referenced herein are either trademarks or registered trademarks of their respective companies. IBM PC is a trademark of IBM Corporation. Windows is a trademark of Microsoft Corporation.

Table of contents

Falcon 2.23 User Manual

Table of contents Chapter 1 -Introduction................................................................................................... 1 1.1 1.2 1.3 1.3.1 1.3.2 1.3.3 1.3.4 1.3.5 1.3.6 1.3.7 1.4

System requirements .............................................................................................................1 Overview ...............................................................................................................................1 Improvements ........................................................................................................................2 Over version 2...................................................................................................................2 Over version 2.13 ..............................................................................................................2 Over version 2.15 ..............................................................................................................2 Over version 2.16 ..............................................................................................................2 Over version 2.18 ..............................................................................................................3 Over version 2.20 ..............................................................................................................3 Over version 2.22 ..............................................................................................................3 Falcon Editions......................................................................................................................4

Chapter 2 -Installation..................................................................................................... 5 2.1 2.2 2.3 2.4

HASP - Protection Plug.........................................................................................................5 Software.................................................................................................................................6 Installation for Multi-Users ..................................................................................................6 Falcon command line options ...............................................................................................7

Chapter 3 -Setup............................................................................................................... 8 3.1 3.2 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 3.4.1 3.4.2 3.4.3

Setting Up the System ...........................................................................................................8 System Layout .......................................................................................................................8 General Parameters................................................................................................................9 Default Settings................................................................................................................9 System Settings ...............................................................................................................10 Communication Settings .................................................................................................10 File and Directory Settings .............................................................................................11 Tools ....................................................................................................................................12 Options ............................................................................................................................12 Importing Personnel files ................................................................................................17 Edit Card Layout (PRO version only).............................................................................18

Chapter 4 -Personnel ..................................................................................................... 21 4.1 Defining parameters for a new employee............................................................................22 4.1.1 Access control tab ...........................................................................................................23 4.1.1.1 Management ...................................................................................................................24 4.1.1.2 General............................................................................................................................24 4.1.1.3 Details .............................................................................................................................24 4.1.2 Taking a Picture (PRO version only) ..............................................................................24 4.1.3 Printing a Card (PRO version only) ................................................................................25 4.2 Department & Company......................................................................................................25 4.3 Calculation Groups..............................................................................................................25

Chapter 5 -Routine Operation ...................................................................................... 28 5.1

Calendar...............................................................................................................................28

i

Table of contents


5.2 Auto Modes .........................................................................................................................30 5.2.1 Auto Mode for Master terminals ....................................................................................30 5.2.1.1 Auto Mode List...............................................................................................................30 5.2.1.2 Auto Mode Detail List ....................................................................................................30 5.2.1.3 Define Auto Mode ..........................................................................................................30 5.2.2 Auto Mode for SY-400 ...................................................................................................31 5.3 Terminal List .......................................................................................................................32 5.3.1 Define a Master Terminal ..............................................................................................32 5.3.2 Define an Access Reader ................................................................................................33 5.3.3 Define an SY-400 Terminal ............................................................................................35 5.3.4 Define an SY-400 Reader ...............................................................................................39 5.3.5 Define a COM-II-PRO Terminal ...................................................................................40 5.3.6 Define an Alarm Controller (PRO version only) ............................................................41 5.3.7 Define an Alarm Detector ...............................................................................................41 5.4 Define a Time zone .............................................................................................................41 5.4.1 Define a Time Zone for a Master Terminal ...................................................................41 5.4.2 Define a Time Zone for SY-400 .....................................................................................42 5.5 Define a Security Group......................................................................................................43 5.6 Define an Employee ............................................................................................................44

Chapter 6 -Communication........................................................................................... 45 6.1 6.2

Sending data to terminal ............................................................................................................... 45

Retrieving data from terminal .............................................................................................46

Chapter 7 -Events........................................................................................................... 47 Chapter 8 -Message Translation ................................................................................... 49 Chapter 9 -Reports......................................................................................................... 51 9.1 Presence/Absence Report ....................................................................................................52 9.2 Transaction report................................................................................................................52 9.2.1 General ............................................................................................................................52 9.2.2 Reader/Security Group/Calculation Group/Population Selection...................................54 9.3 Visitors ................................................................................................................................55 9.3.1 General ............................................................................................................................55 9.3.2 Readers............................................................................................................................55 9.4 Events ..................................................................................................................................55 9.5 Entries..................................................................................................................................55 9.6 System .................................................................................................................................56 9.7 Personnel Security Group....................................................................................................57 9.8 Readers per Security Group.................................................................................................57 9.9 Access Readers Time Zones................................................................................................58 9.10 Duplicates ............................................................................................................................58 9.10.1 Duplicate Cards...............................................................................................................58 9.10.2 Duplicate names ..............................................................................................................58 9.10.3 Duplicate IDs ..................................................................................................................58 9.10.4 Duplicate Photos .............................................................................................................58 9.11 Generator .............................................................................................................................58 ii

Table of contents


9.12 Custom Report.....................................................................................................................59 9.13 Additionals ..........................................................................................................................59 9.13.1 Expire date ......................................................................................................................59 9.13.2 Card Issued......................................................................................................................59 9.13.3 Active Personnel for TimeLOG ......................................................................................59

Chapter 10 -Working Online ........................................................................................ 60 10.1 Online event management ...................................................................................................61 10.2 Clear the online table...........................................................................................................62

Chapter 11 -Visitors ...................................................................................................... 63 11.1 Creating cards via Personnel ...............................................................................................63 11.2 Handling visitors .................................................................................................................63

Chapter 12 -Maintenance .............................................................................................. 65 Chapter 13 -Location ..................................................................................................... 67 13.1 Emergency...........................................................................................................................67 13.1.1 Generate a Fire (emergency) Report ...............................................................................67 13.1.2 Door control ....................................................................................................................67

Chapter 14 -Maps........................................................................................................... 69 Chapter 15 -Fingerprint ................................................................................................ 71 15.1 Hardware .............................................................................................................................72 15.1.1 SY-400 Definitions .........................................................................................................72 15.2 Software...............................................................................................................................72 15.2.1 System Options ...............................................................................................................72 15.2.2 Local Options ..................................................................................................................73 15.2.3 Employee Activities ........................................................................................................73 15.3 Synchronizing Templates ....................................................................................................74

Chapter 16 -Terminology .............................................................................................. 75 Chapter 17 -Troubleshooting ........................................................................................ 76 Appendix A – CCTV Integration (PRO)...................................................................... 77 Regard: Regard i and Regard Remote CS COM interface ..................................................77 NegeVision: VideoRemote..................................................................................................77 Pelco: G-Protocol matrix.....................................................................................................77 Vicon: V1500 ......................................................................................................................78

Appendix B - Database .................................................................................................. 79 Files .....................................................................................................................................79 Extensions............................................................................................................................80 Other Files ...........................................................................................................................80 Foreign Languages ..............................................................................................................80

Appendix C - Upgrade ................................................................................................... 82 Appendix D - Utilities..................................................................................................... 83 Appendix E - Master network configuration............................................................... 85 Telnet procedures: ...............................................................................................................85 Using ARP Command .........................................................................................................86

iii

Table of contents


Appendix F - Error Messages ....................................................................................... 87 Appendix G - SY-Server ................................................................................................ 89 SY-Server Definitions .........................................................................................................89 Falcon Definitions ...............................................................................................................90 DLL Definitions ..................................................................................................................90

iv

Introduction


Chapter 1 - Introduction 1.1 • • • • • • • •

1.2

System requirements Intel Pentium processor or higher Microsoft Windows 95, Windows 98, Windows Millennium Edition, Windows NT 4.0, Windows 2000, Windows XP or Windows 2003. 128 MB of RAM 100 MB of available hard-disk space 256-color (8-bit) display adapter, 800x600 (24-bit – full color recommended) CD-ROM drive Optional sound card recommended for event notifications TWAIN compliant capture card or scanner for Falcon PRO version only

Overview

Managing an access control system with numerous readers and multiple users is a complicated task, especially in a dynamic, ever changing system in which readers are added and moved and access definitions constantly change. Falcon, makes this task easy. It defines access groups in which definitions of all of the parameters pertaining to limited access domains are inserted according to time zones and date, assigning an unlimited amount of access cards (employees) to each group. After a simple update of an access group, an employee is assigned a whole new set of access definitions. Furthermore, when a new reader is added to the system, it is linked to an access group permitting access to all employees within that group. Following is a list of the basic elements of this system: Reader– A unit that recognizes a card code and assigns it to an employee. The reader communicates with the controller and the controller with the PC. Controller– A unit managing the readers in the system. Day type- A template compatible with non working and working day variants as per the enterprise’s definitions and requirements. Time Zone- Defines a time-frame in which access is permitted. Time Zones are defined day types for a period of one year. Security Group- An abstract concept defining Readers and Time Zones to which employees are assigned for the purpose of easy management of the access control system (See System Layout on page 8).

The following symbol will be used in this book to mark features not supported by Falcon Express -

1

Introduction

1.3

Improvements

1.3.1

Over version 2

• • • • • • •

Personnel: A picture can be captured from Falcon 2.12. Printing cards. Tools/Options: A card designing screen (definitions for card printing). Setup/Terminal link: Falcon PRO supports Regard’s CCTV system. Camera name site fields added to controllers and readers. Maps: A new screen graphically displays the terminals location. General: Better operates on a multi-user environment. External Tools: Reindex.exe- For regenerating the index files exterior to Falcon. Falcupd.exe- Upgrading the database of previous versions. Reports - additionals: Expire Date Duplicate Name Duplicate ID Issue Report Entries Report Personnel Security Group

1.3.2 • • • • •

Over version 2.15

Auto Mode for SY-400 Sending updates to SY-400 terminals Substantially improved speed in issuing the Transaction and Presence/Absence reports.

1.3.4 •

Over version 2.13

General: A new SY-400 reader - PRX-30 Personnel: A new Population field in the Employee details screen Tools/Options: Fingerprint verification support Maps: Two separate screens: Edit site and view site enabling easier event management Reports: Open events Response time Old events

1.3.3 • • •


Over version 2.16

Emergency Menu: A new menu for emergency activities.

2

Introduction • • • • •

Operator List: New permissions for door opening/locking. Options: All communication options can be blocked for all computers. Fingerprint: - It is now possible to send an employee template to all SY-400 terminals. - Number of fingerprints per person was increased to 10. A new SMS tab contains modem definitions for sending SMS. Automatic Import: Additional optional fields.

1.3.5 •

•

• •

• • • • •

Over version 2.20

Reports: A very elaborate Transaction report. Duplicate cards report Duplicate Photos report Readers per Security Group report Access Readers Time Zones report Capture signature: an option to work with a signature-pad Support for Pelco and Vicon CCTV matrix (PRO version only) Fingerprint: support for working with Identification and FPU-S units Automatic import: Additional settings Master terminal: Writing with offline lists

1.3.7 • • • • • • •

Over version 2.18

Employee Details: A person can have 5 security groups Automatic Import: Additional optional fields and settings. Reports: Personnel Security Group Report Absence Report Transaction with total report Terminal List: Alarm controller + alarm detectors (PRO version only). Fingerprint: Supports 10 digits template ID

1.3.6 •


Over version 2.22

Employee Details: A new Add Trans. button for manually adding transactions Calculation Group: For managing cost centers Department and Company: Departments can be assigned to employees, and Companies to visitors Visitors: Overall screen change + Possibility to print card for a visitor Reports: Active Personnel for TimeLOG - Enables employee data exportation to TimeLOG FPU: Images can be saved to JPG format, prints can be saved on a Mifare card (validation via card) Options: Support for FPU-S USB reader.

3

Introduction

1.4


Falcon Editions

Below you will find listed the various Falcon editions. In the table specified are the features differentitating these editions one from the other:

Terminals

Event notification

Feature Master + Access SY-400/SY-400A COM-II-PRO Rokonet ProSYS 128 alarm controller Maximum terminals defined SMS

View/Edit site map Localize Adjust Master terminals to daylight saving time changes Auto Modes Define Master auto-modes Time Zones Define Master time-zones Fingerprint Maximal templates per person Card Edit card layout Production Multiple layouts Landscape/Portrait layout Dual-side printing (when supported by printer) Capture pictures via TWAIN device Capture signature from a Wintab supported signature-pad Misc. Maximum cards in Personnel list Visitor module Maximum visitors in list Execute a program when an I/O device is triggered Print/Preview/Export reports Multi user Manual import of personnel data Automatic Automatic import of personnel data scheduling Command line options Online Online data collection from local PRO SYS 128 alarm controller Show live video when card is swiped

Demo + + + + 1

Express

Five

+

+

1

5

+ + + 1 +

2

2

Standard PRO + + + + + + + 255 255 + + +

+ +

+ + 10

+ + 10 +

+ + +

+ + +

+

+ Special

5 + 5

Unlimited Unlimited Unlimited Unlimited + + + Unlimited Unlimited Unlimited Unlimited + +

+

+

+ + + +

+ + + +

+

+ + +

4

Installation


Chapter 2 - Installation To install Falcon under: Windows NT, 2000, XP or 2003, you need administrator privileges Insert the CD into the drive, wait a few seconds for the automatic operation of the installation menu. If the program was not started automatically go to the FalInst.exe file and double click, the screen in the page below appears:

As of Falcon version 2.20 the program requires a hardware protection plug. The HASP key is a hardware device that plugs into the computer and forms part of Falcon’s security. The HASP key protects the user against the unauthorized use of the software and guards against piracy. The HASP key must be installed or the software will not run.

There are two kinds of HASP keys, those that plug into the USB port and those that plug into the parallel port.

2.1

HASP - Protection Plug

Installation can be either: 1. Local per workstation (plug per PC)- requires the HASP driver installation (see FalInst screen). 2.

One HASP on the server- requires the HASP License Manager installation on the server (see FalInst screen).

Note:

Installation can be avoided if the HASP plug has already been installed. If it is a USB port installation you must first install the driver and only than insert the plug.

5

Installation


Click either the HASP License Manager or the HASP driver button. Follow the wizard’s instructions. After the HASP has been successfully installed you can install Falcon software! Note:

To share the HASP using the License Manager, TCP port 475 must be open on both the server and its clients!

2.2

Software

Step 1. Step 2.

Click the Install Falcon button. Navigate your way through the setup procedure. The program automatically runs the setup. If during setup you are prompted to provide information, do so accordingly.

2.3

Installation for Multi-Users

Install as follows: Step 1. Install Falcon into each PC in the System. Note:

Step 2. Step 3. Step 4. Step 5. Step 6. Note: Step 7. Step 8. Step 9. Note:

Follow these guidelines strictly: 1. Open Control Panel | BDE Administrator and in Configuration | System | Init set Local Share as True. 2. Open Control Panel | BDE Administrator and in Databases | Falcon set PATH to the shared database. All clients must use the EXACT same path to the Falcon alias (same drive or UNC name and same case for all clients). 3. Falcon.exe should be run from a local drive, each client running his/her own copy. Drive mapping is not recommended (can be accidently deleted)! Use a UNC name (Universal Naming Connection): \\serverNAME\shareNAME\DB. Connect a PC directly to the terminals, it will be the main station. Define all parameters that create a common central database. Copy this database and the photo files into the server (each under a designated directory). To build a photo file path, click Setup in the pull down menu then choose General Parameters folder. In the Files and Directories section click on the button to the right of the Photos field. Each PC must now create a path to these files in the server. In the main menu click on Maintenance| Restore| Alias to restore. All Falcon stations must share a server under an identical name. Choose the appropriate directory, click OK, confirm the new path. The program will then Restart. For set-up actualization, exit and re-enter the Falcon program. Repeat steps 5–9 to perform setup for each PC in the system. You can not run Falcon twice on the same PC.

6

Installation

2.4


Falcon command line options

Falcon can be operated in batch mode to perform several activities and then close. The syntax is: Falcon [/ai] [/ac] [/au] [/av] [/at]. Available parameters are: /ai = Automatic import of the current personnel data file (a file name can be determined under the Automatic import area in the Import file name field). /ac = Collect data- Collects transactions from all active terminals. /au= Updates terminals - Sends recent (change from last update) updates to all active Master terminals. /av = Send all permitted cards to all active terminals. /at = Sends PC time and date to all active terminals. Windows’ Scheduler could be used to automatically execute Falcon at designated times. To set-up the scheduler in Windows 98, 2000: Step 1. Go to My computer | Scheduled tasks | Add scheduled task. Step 2. Using the scroll bar find Falcon software and mark it. Step 3. Click Next. (You can give the task a name other than the default name). Set frequency, click Next. Step 4. Set Start time, frequency and Start date and click Next. Step 5. Fill-in a user’s password (qualified) in the Enter the password field. Step 6. Check the Open advanced properties for this task when I click finish check box. Click Finish. The task screen will appear. Add a slash “/” and the relevant command line parameter/s. Note:

When you execute Falcon with the AT command it runs as a service, which does NOT have mapped drives! Thus, if you set your alias in G:\db it will work in interactive mode but will fail when run from AT because it can not find drive G.. Therefore, you MUST use UNC names for all clients (and server) alias.

To set-up the Scheduler in Windows NT: Step 1. Open the Command prompt. Step 2. Type the following: AT hh:mm [/EVERY:date] x:\Path\Falcon.exe [/ai] [/ac] [/au] [/av] [/at]. i.e.: For data collection from the terminals at 1AM in the morning every Monday type: AT 01:00 /EVERY:M c:\Falcon\Falcon.exe/ac Note:

For NT, 2000, XP make sure that the schedule service is started (ask your system administrator for help) and logged-on as a user that has authorized access to this data. Since the default “System Account” user does not have access to network resources.

7

Setup


Chapter 3 - Setup 3.1

Setting Up the System

Before initiating setup it is recommended to plan the optimal system structure: Outline reader location according to which the controllers will be placed. The employee list should be sorted out according to a logical order: per department/job title/location. A general planning of time and location requirements for access control generation must be laid out. Yet, as a preliminary stage it is recommended to allow all employees overall access, and after a trial period start the secondary stage of adjusting access control parameters. As authorization parameters are dynamic they should be changed gradually.

3.2

System Layout Employee Employee Employee Security Group

Security Group

Controller

Reader

Reader

Reader

Reader

Controller

Reader

Reader

Reader

Reader

Begin the Setup Click the Setup icon in the main tool bar (Setup can alternately be chosen from the menu). On the left side of the screen 11 folders are listed. These are regulation folders that will help you set-up your system. You can set up your system in the order the topics are outlined herein.

8

Setup


The folders are: General Parameters

Security Group

Calendar

Events

Auto Modes

Communication

Terminal list

Report Generator

Time Zones

Message Translation

The high-lightened modules are complementary and optional.

3.3

General Parameters

These enable you to define the global settings which affect all Falcon stations. The definitions for General Parameters are divided into 4 categories: Default Settings System Settings Communication Settings Files and Directories

3.3.1

Default Settings

Refers to the default settings of your Falcon system which are automatically used when defining a new terminal. When you need to change parameters of a terminal or to define a new terminal, default definitions can be replaced according to your preferences in the Terminal List.

Terminal section: This group contains fields that affect default settings for new terminals. Format- You can choose one of the formats found in the PHANTOM.fmt file. Port- Defines to which communication port the controller unit is connected. Baud Rate- Defines the communication baud rate Duress Code - A code used by a user threatened by an outsider. After keying-in this code the door is opened and simultaneously an event is sent to the host computer. Used by Access reader in Card+PIN mode. Maximum Cards - The total amount of cards used in a master terminal. Global Anti-Pass-Back- Enables preventing more than one entrance through the same door (for all readers connected to the same controller) until the same card is used at one of the other terminals defined in the Terminal Dependencies table.

Card section: Consists of the location and length definition of the string of digits to be read by the slave terminals, includes also the expiry date. Start- The location of the first character to be read from the card. The part of the magnetic string that will be read and included in the default definitions. Length- The number of characters in the string to be read. Max. Length- The total number of characters on the string. Expire Date- The default expire date for new employees. Set Group- A default security group for all card holders.

9

Setup


Set Visitor Group- A default security group for all visitors.

3.3.2

System Settings

The fields in this group define settings that affect Falcon's interface with the PC and the outside world.

Localize section Language-The selected language is used for text displayed on the PC. Choose also the view direction of the user interface. Summer Time/ Winter Time-Determine whether and how terminals will be adjusted for Daylight Savings mode.

Card design (PRO version only) section Generate Picture Name from Index- For proximity cards, enables generating a picture name into the employee’s index number instead of his card number (until you print the proximity card you do not know the card number). Photo Ratio- The default ratio used for capturing a persons picture is 0.77, you can change it to 0.75.

Company name for reports If you wish to add a company name header to your reports, fill-in the name here.

Fingerprint section FPU Type- There are different fingerprint validation methods, choose one for all readers as per the terminal type in your disposition. For further information see Fingerprint, on page 71. Templates per Person- Determine how many fingers can be enrolled for one employee. Show Template Image- Whether to show the template image after enrolment (Employee screen). By viewing the enrolled template the enroller can determine if the template quality is sufficient, or a reenrolment should be performed. Also, if enrolment is problematic, the origin can be traced (finger, unit etc). Save Template Image- After enrolment template images can be saved in JPG format under the same directory as the fingerprint templates. To change the path see 3.4.1.4 Fingerprint, on page 15.

Display these Terminals section It is possible to disable all terminal types which are not used in your system. By default the Master controller and its Access units are displayed. All relevant parameters will be disabled accordingly.

3.3.3

Communication Settings

Communication Section Retry- Represents how many times the communication program tries to execute a command in case of an error. Time Out- The amount of time (in seconds) the host waits for controller response. Time between Blocks- Waiting time (in milliseconds) between consecutive blocks while communicating with a terminal. Remote update- Enables updating Personnel data to terminals from remote workstations. When sharing your DB with more than one workstation, only one station can communicate with terminals. New data is accumulated, and during an update the communication workstation reviews it and sends the relevant data (implemented differently for each terminal type) to the terminal. In your communication workstation you must: Go to Tools | Options | Automatic Scheduling | Frequency, under Update Terminals and set a frequency value larger than 0. Choose what terminal type will be updated. For each terminal type updates will be performed differently:

10

Setup


•

None - No updates will be sent automatically. Updates can be sent (when required) manually via the Communication screen or via Personnel | Send Last. This option is relevant when you are working with one PC only which is connected to a Master terminal, or if there is no need for recurring updates. • Master - The PC will send all updates as of the last update . • SY-400 - The PC will send all accumulated updates as of the last full programming. • COM-II-PRO - The PC will resend the whole authorized list to all COM-II-PRO terminals. Save Comm Errors in DB- Mark this check box for saving online communication with controller errors in the DB, while creating a corresponding event. Write Last Transaction into Personnel File- Writes the employee’s last transaction in the employee record. It decreases the counter for employee type Active - countdown. When the counter reaches zero the program will change the employee type to Countdown reached 0. This information can be found under: Personnel | Employee details | Management. This information will be used later in the Absence report. This procedure does not update the terminal. Thus: • Master terminals have a counter and require this procedure only for updating the PC. • SY-400 terminals can either: Use SYServer for online counting OR PC counting will be updated in the terminal by regularly sending it the authorized list. Note:

As this procedure requires an employee search it might slow down data collection!

Send Visitor Cards to Terminal- If this check box is marked (default), then while issuing/returning visitor cards the status of the card in the Personnel list will change accordingly and will be sent to all active terminals (Immediately to Master terminal and during updates to SY-400 terminals). Note:

For SY-400 terminals, it is recommended to uncheck this box, and thus keep all cards available at all times!

Enforce Induction Date- the time measured from the last periodical safety recertification date. After that time the employee will be blocked until he is recertified.

Master Parameters Section Door Button Group- In Master terminals, assigning a security group to a terminal enables operation of its door button for the predefined time for that group. Note:

Two events are dedicate to indicate the use of door buttons: - Door opened by button - Unauthorized door button

SY-400 Parameters Section Techncian card- The defined number will be used as the technician card number for all SY-400 terminals.

3.3.4

File and Directory Settings

This folder contains the path for each of the following files: Phantom Path- Location of the system communication program (Phant32.exe) Data- Location of Transaction. Backup- The location of Transactions backup file. Project Directory- Refers to the location of the Tables directory. Photos Directory- Location of photographs. Signatures Directory- Location of signature copies (PRO version only).

11

Setup


3.4

Tools

3.4.1

Options

This feature enables regulating your local workstation settings and parameters (does not affect other workstations!): 3.4.1.1

Fonts

Enables defining interface (Toolbar, setup-bar, status-bar) font size and type. 3.4.1.2

Automatic scheduling

All automatic activities are regulated in this screen as follows:

Frequency section • • •

Sends PC time and date to the terminals. Update Terminals- Sends recent (changes from the last update that includes also new fingerprint templates) updates to all active terminals of the type selected under Setup | General Parameters | Communication | Remote Update. Collect Data - Collects transactions from all active terminals.

Automatic import section Automatic import of the current personnel data file (a file name can be determined under the Automatic import area in the Import file name Field). This file is created by another program, the Falcon retrieves the relevant data and deletes the update file. Each person’s data appears in a separate line, commas/tabs inbetween fields and each line ends with CR+LF.

12

Setup


The fields are: Card-number, Name, Type, Group-1, Date-1, Time-1, Description, Department, Position, Employeenumber, Photo, Pop-type, Phone, Cell-Phone, PIN, PIN-Required, Group-2, Group-3, Group-4, Group-5, Date-2, Date-3, Date-4, Date-5, Time-2, Time-3, Time-4, Time-5, First-name, Middle-name, Family-name, City, Street, House-Number, Apartment, Zip-Code, District, Birthday, InductionDate, Signature, Expected- Swipes. Below please an elaborated explanation regarding the main fields: Type: -3 -2 -1 0 1 2 3

Stolen Countdown reached 0 Suspended Blocked (not active, it is impossible to delete cards by importing) Active Active countdown Active offline

Group (1-5): Security group name or ID (If you fill-in 0, you will clear current security group. Leave this field empty to get the default security group): Note:

The group ID can be viewed in the Readers per Group report or from the Edit Security Group screen (bottom left side).

Date (1-5): Optional expire dates (per security group), must be in either: • A Windows format as defined under: Control panel | Regional settings | Date | Short date format. • A fixed format: YYYY-MM-DD Time (1-5): Optional expire times (per security group), must be in HH:mm format. Description: Any relevant information pertaining to the card. Population type: 0 - Regular, 1 - Visitor, 2 - Guard PIN: Four digit personal code PIN Required: 0 - check box in Employee details screen will be unmarked. 1- check box in Employee details screen will be marked. All fields except card number are optional. Make sure all irrelevant fields are empty and the system will disregard them (The system disregards leading and trailing spaces). Fields containing commas (for example: Description) must use quotation marks so that the software addresses the text within the quotation marks as one field. i.e: 123456, "Kedem, Chen", 1 in order to skip a field with no update leave its space empty: 123456,, 1 in order to delete the field content: 123456, " ", 1 (note the space between the quotes). Default Security Group: As part of the import process you can define a default security group for all newly imported employee files in the Default Security Group field as follows: • If it is a new employee the program will insert the default security group number. • If it is an existing employee the security group no. will not change. Exclude the First (Header) Row when Importing- When importing Excel CSV files you can exclude the header which is usually the title row from your destination file. Search Key Field- Matching current database and imported database is done according to either card number or ID number keys. For card number the software checks that each number is unique. Yet, for ID

13

Setup


number it is the operator’s responsibility to make sure IDs are unique! File Type- You can import either from a comma delimited source file format (CSV) or a tab delimited source file format. Date Format- You can import either a source file Windows date format or a fixed format: YYYY-MM-DD. 3.4.1.3

Online

Enables defining online settings as follows:

Disable Communication with Terminals- All communication activities can be disabled per workstation. Start scanning on Program Startup- Marking this check box initiates terminal polling. Scanning is activated when the software is starting. Online Scan Delay between Terminals- Time spent in-between terminals during online scan. The delay makes CPU time available for other tasks. If you fill-in a value smaller than 300 ms this might overload your PC. Network scan - Screen Refresh Delay- The delay between refresh to refresh. Event signalling frequency- The frequency for other workstations event scanning. Generally employed only for workstations, not for the PC that collects the data (because this PC initiates sending these events) for activating popup messages and notification sounds. 0 = no operation - for single-user operation or for operators who do not require event notification. Disable Event Sound Indication- Disables any defined event sound indication. Disable Event Popup Indication- Disables any defined event popup indication. The following items are dedicated to tracing any problems that may occur in your software: Append Information into Phantom Log File- Enables saving Phantom Logs indefinitely (If this check box is unmarked phantom.log will be cleared and re-written for each Phantom activity. Create SynDLL Log File- The syndll.log registers online data. The accumulated data can be of high volume, therefore it is recommended for use only to trace problems. Create Phantom Debug File for SY Terminals- The synelcom.log documents all SY-400 low level communication activities. It is cleared whenever Phatom is activated.

14

Setup 3.4.1.4

Falcon 2.23 User Manual Fingerprint

see Chapter 15 - Fingerprint, on page 71. 3.4.1.5

Daily

Daily Database Backup Section Possibility to copy, once a day, all databases to another directory for backup purposes. The system signals all workstations to close their database temporarily to ensure successful backup. The backup directory can be fixed, than it will be overriden during backup. It is also possible to fill-in a variable in the Destination Directory field as follows: %YYYY% %YY% %MM% %DD% %W%

Current year in a four digits format. Current year in a two digits format. Current month in a two digits format. Current day in a two digits format. Day of week while: 1= Sunday, 2= Monday etc.

Create Destination Directory- If no destination directory exists, it will be created. If the check box is unmarked make sure a destination directory exists before the backup starts. Thus, each time a new file name will be created, and the old file will not be deleted. After backing up has been completed it is possible to execute an external program (For example: for file transfer/deletion, etc.).

Daily Sending of All Permitted Section Sending all authorized employees details to all active terminals once a day. 3.4.1.6

Grids

Enables saving/not saving user grid preferences: Use default settings- The software uses the default set in the program’s exe file. Load user settings from disk- the software uses the changes made by the supervisor (in Load user settings from disk. Save settings on exit), but does not save any additional changes. Load user settings from disk, save settings on exit- changes made by the user will be saved every time on exit.

15

Setup 3.4.1.7

Falcon 2.23 User Manual SMS (PRO version only)

The Short Message Service is similar to paging. It is a service for sending short text messages to mobile phones. Currently Falcon uses: 1. Ericsson DM-10/DM-20 SMS modem. 2. GSM devices. Firstly, you must define all SMS communication parameters under Tools| Options| SMS as follows: Port Baud rate - usually 9600 Time out (between transmissions) - must exceed 2-3 seconds - time for message transmission + reply for SMSC. SMS modem - choose a compatible modem. Message encoding - setting sender encoding. If it does not match receiver encoding the message will not be received or be received obscurely: • IRA (International Reference Alphabet) - English language alphabet • ISO 8859-1 - Latin 1 - covers most west European languages • ISO 8859-8 - LATIN/Hebrew - used by Hebrew and Yiddish • Unicode - provides a unique number for every character, no matter what the platform or language. Now, you must plug-in the modem into the defined PC port (RS-232 port). In Falcon, SMS messages are sent during an event. To send a message you must do the following: Step 1. Go to Event | General, the event description will be the content of the corresponding SMS message. Step 2. Define the event and fill-in the content of the message. The message will also contain: date, time, card number and the terminal involved in this event. Step 3. Under Event | Automatic Activity you can choose to which subscriber the SMS message will be sent (After you have manually filled-in all relevant subscriber mobile phone numbers - a number per row! You can use the semicolon for sender remarks as text to the right of the; symbol will not be visible). The Test button is used for sending a test message. The designated subscriber/s must then check if it was received correctly and fully. 3.4.1.8

I/O Card (PRO version only)

Falcon uses a standard RS-232 serial port or a dedicated data acquisition card to sample an input signal. When the signal changes it executes an external program and/or open all emergency doors. For example when a fire alarm system circuit closes Falcon will open all doors and run a fire report program. Two different card types are supported by Falcon: • RS-232 serial port sampling of an CTS input signal. For operation use either pins 5, 8 on a DB9 or 5, 7 on a DB25 connector, to be powered over 3-12Vdc. • ADLINK’s PCI-7250 digital data acquisition card for sampling of digital inputs. If you are working under Windows 95’, choose Win 95 only, otherwise choose the other option. (For installation refer to the manufacturer installation instructions). Set the device‘s operational parameters: Step 1. Choose the relevant card type and its designated port. Step 2. Sampling rate: frequency of signal sampling. Step 3. Input Active State: High/Low are the electrical level to be sampled. Toggle - any change will trigger reaction. Step 4. Click the browse button in the Command Line to Execute field to insert the path of the program to be operated.

16

Setup Step 5. Note:

3.4.2

Falcon 2.23 User Manual If you want all doors to open during an emergency, mark the Open All Emergency Doors check box. The SMS/Fingerprint/I/O card features are RS-232 port designated.

Importing Personnel files

Falcon enables importing text files for registering new employees either manually or automatically (see 3.4.1.2 Automatic scheduling, on page 12). These import methods differ in file structure. Also, in automatic import the imported file is deleted after reprocessing. The manually imported text files are based on a user defined template. Where each line in the file is a record for one person, each field is in a fixed position and a CR+LF at the end of the link. The import procedure is as follows: Step 1. Click on Setup, then click on the Personnel folder. Step 2. In the Personnel screen click on Import; the Open screen is displayed.

Step 3.

Select your (previously created) Import text file; the Import screen is displayed (below).

Note:

The particulars of the first line in the import file appear under ASCII File Structure title.

Step 4. Step 5. Step 6.

To continue with the importing process, mark an item of datum, then double-click on the Type space opposite the relevant title. Repeat this for all remaining data items. To update the following employee details click Next icon.

17

Setup


Step 7. Step 8.

For a display of the new names click on the View ASCII button. Click Import at the bottom of the screen; the ASCII file was now imported into the program database. Click Close to exit the import function.

3.4.3

Edit Card Layout (PRO version only)

You can edit the card layout in Tools | Edit Card Layout, then in Personnel | Employee details | Management | Card layout assign a specific design to an employee.

First you must decide if you want the card printed Landscape or Portrait. Later you will set the dimensions accordingly. There are two different card settings, Personnel and Visitor. Below indicated are the differences between them: Personnel Card

Visitor Card

Photo

--------

Signature

--------

Department

Company

ID number

Host Name

Calculation Group

Host Department

Police Clearance

Escort Required

There are four tabs: General, Fixed fields, Extra fields and Back side. Use the following buttons for navigation and editing: • •

Revert to previous Card Layout Forward to next Card Layout

18

Setup


• Insert a new Card Layout • Delete current Card Layout • Save changes • Cancel changes from last save. General Mark the relevant check box and fill-in the Banner*, Company logo, Falcon logo, Photo and signature fields. *

The banner is where you can write text on the card. Aside from plain text that can be simply filled-in, It is possible also to encode magnetic cards or print barcodes using the compatible printer, using the following macros: {Number}

Inserts the value of an ASCII character as specified in the brackets. i.e.{64}=@

{%Field name, start from, length}

Field name-

Fill-in a field name from the employee file. i.e. Description.

start from-

Display offset for the defined Field name (if you want only part of the data to be displayed).

length-

How many characters to be displayed from offset point. If no value is filled-in the whole field will be inserted.

Fixed fields Mark the relevant check box and fill-in the Person name, Card number, Department. Extra fields Mark the relevant check box and fill-in the Extra fields 1/2/3/4. Note:

To print the current date you must select ISSUE_DATE from the Field Name field.

Misc.

You can use this optional tab for back-side printing on supported printers. In the Picture field, choose a background photo.

19

Setup Note:

Falcon 2.23 User Manual Dimensions are in pixels. Template will be in alphabetic incremental order (as per template name).

Name Card number Department Falcon logo

Company logo (background)

PHOTO

Falcon - Complete Systems Control Falcon banner

Police Clearance/Escort Required There are two fields: Yes and No. Assuming that this check box is marked: The content filled-in in the Yes field will be printed if the equivalent check box under Employee Details | Details or under Visitors is marked (under the fields: Police Clearance or Escort Required), and the content filled-in in the the No field will be printed if these check boxes are unmarked. Print Offsets Enables shifting of the edited layout as a whole, on the card frame. The change will be evident only after printing (will not be reflected on the Edit Card Layout screen or on the Preview screen).

20

Personnel


Chapter 4 - Personnel Under Personnel you can open Employee files that include all information regarding the specific employee, organization-wize and also persoanl information. See the screen below:

On the right-hand side of the screen you can filter the employees by their population type: Regular, Visitor or Guard or not filter at all. See right-hand list for sorting employee data.

21

Personnel

4.1


Defining parameters for a new employee

1

4

2

5

3 8

6 7 9

10 13 15

11 12 14

The Employee details screen in the Personnel folder enables opening a new employee file as follows:

22

Personnel

4.1.1


Access control tab

Ref. Field name

Description

1 2

Card number Card type

3 4 5 6

Description Name Population Pin/count

Employee encoded card number. Assign a card type (terminal induced) to an employee: Stolen- An inactive card that can be treated as stolen when working with SY-Server. When marking the Capture check box, the employee will be allowed to enter and then he/she can be “captured”! Countdown reached 0- The card is blocked after entry counter reached 0. Suspended- Temporary blockage by operator or system. Blocked- A permanent blockage by operator. Active -Regular- Working in the organization on a regular basis Active -Countdown- Working temporarily and allowed to enter/exit a preset number of times (Master only) For complementary information (SY-400) see paragraph 3.3.2 System Settings, on page 10. Active-Allowed offline- this card type will be sent to the Access units to be stored there when there is no communication with Master. Free text. Card holder’s name and surname. Refers to the card holder’s position access control derivatives. As per card type: Regular - pin-code - an additional keyed-in classified code Count - Count - Designated access limitation

7

Capture Cardholder Allows a card holder to trigger an event in the relay logic (relay 2) (Master only)

8

Disable Fingerprint When this check box is marked the employee will be able to enter the premises without check a fingerprint requirement. Security group An employee can be assigned upto 5 security groups. For further information see paragraph 5.5 Define a Security Group, on page 43. Expire date/time Later than this date the card will no longer be valid for the specific security group. Photo The path for the employee’s photo. Signature An option to work with a signature-pad that supports the Wintab protocol in order to grab the employee signature (aside from the hardware, a special Falcon license is also required), or working with a TWAIN device similar to the Capture Photo screen. Choose the path for the employee’s signature (PRO version only). System Report A report showing the active doors for this employee.

9 10 11 12

13

.

23

Personnel


Ref. Field name

Description

14

Add Trn.

Enables adding a manual (will be marked accordingly) transaction for this employee. See screen below:

15

Print Details

Prints the content of all 4 tabs on one page.

4.1.1.1

Management

Consists of data pertaining to employee database management: ID number, name, department (see paragraph 4.2 Department & Company, on page 25), position, extension, card layout and other card related data [assign one of your predefined layouts to this specific card, see paragraph 3.4.3 Edit Card Layout (PRO version only), on page 18], e-mail, cell phone, comment. Also included are several employee monitoring parameters as follows: Induction Date- Fill-in the last periodical safety recertification date. The period length is determined under Enforce Induction Date field, see see paragraph 3.3.3 Communication Settings, on page 10. A person is not valid unless inducted in this field. Expected Swipes- A means of monitoring employee swipes over a specified period. For further information see paragraph Swipe Count per Person, on page 54. Last transaction- The employee’s last transaction is displayed here (see paragraph 3.3.3 Communication Settings, on page 10). Capture Date, Card Issue Date, Cards Issued- The information is complimented systematically when these procedures have been performed, and is used for follow-up.

4.1.1.2

General

Personal employee information such as address, birthday etc.

4.1.1.3

Details

Consists of additional administrative information. Also, it is possible to indicate the location of an external text file.

4.1.2

Taking a Picture (PRO version only)

The Falcon PRO enables taking a picture of an employee or any other card user for final identification, and also preparing an employee card. Use a scanner or a frame grabber that supports a TWAIN interface (such as Video Associates Labs VideoVue card). This can be done as follows: Scanning A picture can be scanned and saved in your PC and then inserted into your employee file. Step 1. Make sure scanning hardware/software devices are available in your system.

24

Personnel


Step 2. Step 3.

Click on the relevant employee row. Place the required picture in your scanner. Click on the Capture button, you can right click Grab picture and choose the required capturing device. Scan the picture and save, the picture will be placed in the personnel file under the chosen row and saved in the photos directory and will be saved in the Photos directory. Import an existing picture file You can use a picture from an existing JPG or BMP file as follows: Step 1. Upon double clicking on the employee row, the Employee Details screen will appear. Step 2. In the Photo section click the icon, locate the saved file and click Open. Pasting an existing picture from your clipboard If a BMP file is stored in the clipboard, you can paste it into your Capture photo screen (CTRL+V). After you clicked on the Capture button.

4.1.3

Printing a Card (PRO version only)

Step 1. Step 2.

For printing a card click Print card in the Personnel folder. Choose the relevant printer, and click Print.

4.2

Department & Company

You can add a department or company by either: • Go to the Personnel menu | Department and Company, click the New button and fill-in a department name, OR • Go to Employee Details | Management or Visitors | Visitor Details and simply fill-in a Department/ Company name. Departments will be allocated to employees, companies will be allocated to visitors. Note:

4.3

Changes made to these databases will not be comprehensive (i.e.: If you change a department name, you will have to do that for all employees who were assigned to this department).

Calculation Groups

Define calculation groups A Calculation group is a possibility to categorize a group of resource users. These groups can be managed and followed up, and reports can be issued per group. Under the Personnel menu go to Calculation group List, the following screen will appear when you edit a group:

25

Personnel


Each calculation group consists of up to two independant categories. Step 1. Fill-in the Description field to name your calculation group. Step 2. To enable counting limitation, you must define a Minimum Value and a Maximum Value. The Add Trn. button enables adding a manual transaction that will be updated for all employees who are assigned to the specific calculation group. i.e.: If all employees have finished working, it is possible to report Exit for all of them at once. Assign to an employee Go to: In the Employee Details screen under Management choose the relevant Calculation Group. Assign calculation categories to the relevant readers Calculation categories can be assigned to each reader as follows:

26

Personnel •

SY-400

•

Access Commonly reader A is used for Entry and reader B for Exit.


• COM-II-PRO Each function key can be assigned a different calculation category.

27

Routine Operation


Chapter 5 - Routine Operation After the Set-up procedure has been established, there are regular activities involving data coding in the different folders as follows:

5.1

Calendar

The calendar was developed and incorporated into the Falcon system to grant greater flexibility to the user by defining broader access parameters. In addition to its flexibility, the Calendar allows long-term programming. Falcon enables defining and programming every day of the year with specific access parameters for irregular hours and days such as: Holidays, weekends. The same time zones can be used every year, in case adjustments are required they are updated in the calendar folder. In the past, access was defined: Date >>Day of the Week>>Hours Of Access Now access is defined: Date >>> Type Of Day >>> Hours Of Access SY-400 and Master terminals receive information from the calendar and use it for Time Zone and Auto Mode settings. Defining a day type A day type definition applies to full or half vacation days and other exceptional days. The system supports 9 working day types. A Master uses only the first seven days. Step 1. Enter Setup via the menu. Click on the Calendar option. The Calendar screen appears. Step 2. From the menu click on the Customize button and then on Day Type; the Day Type screen is displayed (below).

Step 3.

Click on the Day Type tab. In the Day Type screen you can add or change the required day type and the day color indication (Each day is already color marked. You can change the coloring by double clicking and choosing another color. Click OK. Day Definition Enables setting a day type default definition for every day of the week.

28

Routine Operation

Step 1. Step 2. Step 3. Step 4. Step 5.


Click on the Day Definition tab. Choose the first day of the week, then enter the day type for each day of the week, this will be the system’s default definition. Enter the year you wish to define. To change a single day type mark the Edit Calendar check box in the Calendar screen. The Calendar displays the colour-coded days that were programmed by you. Here you may proceed and choose special days and holidays. Mark the Assign Group check box, and select a day type. Than click on all days to be assigned to the specific day type you just chose. The colour of the squares changes accordingly.

29

Routine Operation

5.2


Auto Modes

This folder, which is used for Master and SY-400 terminals, defines the input mode of the terminals. The terminal will change its operation mode according to the specified time and date.

5.2.1

Auto Mode for Master terminals

The Master Auto Mode screen is divided into two main tabs: Auto Mode List and Auto Mode Detail List Each Auto Mode consists of one or more definition lines.

5.2.1.1

Auto Mode List

The Auto Mode List enables automated transition between a combination of predefined access modes.

5.2.1.2

Auto Mode Detail List

The Auto Mode Detail List is for defining hour and day parameters dedicated to particular Security Access Measures. Following are the predefined access modes: Card- By card alone Code- By employee number Card and Code Card and PIN- + An additional code Code and PIN Card or Code and PIN Closed- No entry allowed Force Door Open- Constantly open Card plus card- Entry with an escort

5.2.1.3

Define Auto Mode

You can define an Auto Mode for a Master terminal both with and without using the Calendar. To program Auto Mode using the Calendar you must first enter Setup | Terminal List, double click on a

30

Routine Operation


Master, then click on the Additions tab and the Yes radio button in the Use calendar area. To program an Auto Mode for a Master, click on Auto Mode; the Auto Mode screen appears (above). In the fields From Time and To Time define the hour range in which the Auto Mode will take place. In fields 1 through 7 define the type of day by which the programmed conditions will operate. In the Auto Mode Type field, enter the Auto Mode type you wish to use. Note:

Make sure that the whole 24 hour time range is divided in full into time zones. For example:

00:00-06:00Card + code 06:00-18:00Code 18:00-23:59Card + code In the example below each number and the corresponding field below it represent a day type. The first day type in this example is “Normal Day” which represents Monday through Friday.. From Time To Time

1

2

3

4

5

6

7

Auto Mode

6:00

+

-

-

-

-

-

-

Code

18:00

In order to program an Auto Mode without using the Calendar enter Setup | Terminal List, click on New at the bottom of the screen, then click Additions, and click the Without Calendar radio button. In this case, defining an entrance access between the hours 6:00 - 18:00 for all days, excluding Saturday and Sunday will be displayed as shown below: From Time To Time

1

2

3

4

5

6

7

Auto Mode

6:00

-

+

+

+

+

+

-

Code

5.2.2

18:00

Auto Mode for SY-400

It is easier to match an auto mode to a day type as the differences are visible. Step 1. Click on the SY-400 tab. To add a new auto mode click New; a new line is added to the Auto Mode List column, fill-in the appropriate name.

31

Routine Operation Step 2.

Note:


In the Auto Mode Details chart mark the Edit check box, and make sure that you are using the relevant auto mode type. By clicking and dragging the mouse, mark the days and hours you wish to define (the chart is comprised of 30 minute time units). While surfing the mouse across the chart, you can see its exact location indicated at the bottom of the chart (day type, hour and access mode).

Access modes: Default - Corresponding to the reader validation definitions. Card Card and PIN Card and Finger Card+PIN+Finger Card plus Card Force door open - The relay is active all the time (See reader’s definition). Closed - The reader is disabled.

5.3

Terminal List

This module enables defining the system’s access control parameters for all terminals (Master, SY-400, COM-II-PRO, alarm) and their readers as follows: Note:

You can copy a terminal including its subordinate readers by right-clicking your mouse on the relevant terminal in your terminal list.

5.3.1

Define a Master Terminal

Step 1. Step 2. Step 3. Step 4.

From the menu choose Setup. In the Module List choose the file Terminal List. Click on the Master + Access tab on the Terminal List screen. Click on New at the bottom of the screen; the Terminal Setup - Master screen is displayed including four tabs.

General Step 1. Step 2.

Choose the General tab and fill-in the ID and Name of the terminal. In the Trans File Name field choose a destination text file name to which the transaction will be exported. Step 3. In the Format field select Master or any other appropriate format from the drop-down list. Normally, this will already have been done in the initial set up of the system). Communication Step 1. Choose the Communication folder tab. Step 2. In the Connection Type section choose a communications type: Local - the COM port and baud rate must be defined. Modem- Enter the telephone number and an optional Init. string. Network- TCP/IP communication- enter the address and the port in use (usually 3734). Cards Step 1. In Cards | Start from field enter the placement number from which a card number will be read to the transaction File. Step 2. In the Length field fill in the number length (from left to right).

32

Routine Operation


Additions Duress Code- The emergency code that allows access to all cards, while registering a:Duress code” event type. Max Cards- Indicates maximum amount of permitted cards. Note:

For Master-128 do not fill-in a value that exceeds 2976. For Master-512 do not fill-in a value that exceeds 14000.

Activate Anti-Pass-Back- Prevents a card from being swiped twice in the same reader. Enables anti-passback for all readers pertaining to a specific Master. Send offline lists to Access units- Authorized lists can be marked and then sent to Access units, to enable door opening regardless of communication with Master. Note:

As of Master version 3.20 and for compatible readers.

Use Calendar- Indicates if this Master supports a calendar (The earliest Master firmware version which supports calendar use is 3.15). Relay Logic- A possibility to use an external configuration file that contains relay logic definitions. The user can define which events will be sent when Input/Output changes. For further instructions for writing a configuration file refer to the Phantom documentation (RelayLog.txt). Automatic Data Send- When working with SY-Server: As of firmware version 2.22, transactions and queries can be initiated every couple of seconds in Online mode, or none in offline mode.

5.3.2

Define an Access Reader

Management


Enter into Setup mode and click on Terminal List. Click on the Master folder. On the Access list screen click New; the Access Setup screen is displayed. On the Access Setup screen fill-in the ID field. In the Name field enter a name of your choice to represent the reader location. In the Reader/s field/s enter the relevant mode.

33

Routine Operation Note:


When either reader is marked as None, all transactions from that reader will be stored in the Rejected.nnn file.

Step 4. Under Model choose which controller will be used. The Door Monitor section, defaulted as None, controls the Open/Close status of a door sensor. Depending on the type of door sensor in your disposition, you may have your sensor in either the Normally Closed or Normally Open position to make it operable. Door Opening Time- Defines the time interval in which the door relay will remain open in 0.1 second units. Door Monitoring Time out- Defines the maximum time period (in sec.) door opening is allowed before the alarm is activated. Allow Emergency Open- Marking this check box will enable opening the door during an emergency for further information see Chapter 13 - Location, on page 67. Global Code- When the Access reader is in Card+PIN mode and an employee does not have an individual PIN code, this code is used instead. Thus, a specific group of employees that knows this code can use it to enter that door. Under the Auto Modes- Enables selecting a preset auto mode: see see 5.2 Auto Modes, on page 30. Anti Pass Back- Enables monitoring access by defining access routes for each employee. This can be done only between Access readers pertaining to the same Master terminal, provided that the Activate AntiPass-Back check box is marked under Master definitions. For each Access, a list of all readers managed by the same terminal, and determine from which reader access is permitted. A card that will be swiped in the current reader will be permitted, only if the previous reader was marked in the current reader set-up screen. Note:

If no reader in the list was marked, access will not be allowed via this reader.

Thus, it is possible: • To prevent unauthorized entry by disallowing 2 continuous entries/exits via the same reader. • Defining access co-dependencies between readers to enable routing employees on site. You must set permission definitions per reader, via which reader passage will be allowed. For example: To enable access via a specific reader your must define backwards: if you wish to allow passage via a reader you must mark it in the reader that passage-chrono-wise comes before it. For example: To enable passage from Reader A to Reader B, to Reader C and back to Reader A, mark as follows: In Reader A Set-up screen:

In Reader B Set-up screen:

In Reader C Set-up screen:

Reader C

Reader A

Reader B

Similarly, you must define all other readers.

34

Routine Operation


Optional

To define a Calculation Category, see 4.3 Calculation Groups, on page 25. Camera site (PRO version only)- The name of the camera server associated with readers, that is integrated with the CCTV system (case sensitive). Camera name (PRO version only)- The name of the camera associated with the specific reader (case sensitive).

5.3.3

Define an SY-400 Terminal

Step 1. Step 2.

From the menu or tool bar choose Setup. In the Module List choose the file Terminal List. Click on the SY-400 tab at the top of the Terminal List screen. Click New; the Terminal Setup SY-400 screen is displayed including the following folders:

General Step 1. Step 2.

Choose the General tab. Fill in the ID and Name of the terminal. In the Transaction File field choose a destination text file name to which the transaction will be exported. Step 3. Select the relevant format from the Format combo box. Step 4. The Query File optional field will be used by the SY-Server as an auxiliary file for writing queries (an advanced feature). Communication

Step 1. Choose the Communication folder tab. Step 2. In the Connection Type section choose a communications type: Local - the COM port and baud rate must be defined. Modem- Enter the telephone number and an optional Init String. (When using Synel’s standard built-in ISOMODEM you can fill-in the predefined init string: &FE0V1) Network- TCP/IP communication- enter the address and the port in use (usually 3734).

35

Routine Operation


Cards

Step 1.

Choose the Cards tab. In the Start from field fill-in the placement number from which a card number is read to the transaction File. Step 2. In the Length field fill-in the number length (Left to right). Step 3. In the SY-400 section, mark either Fixed or Variable. For Variable you must further define Padding parameters. Then, in the Max. Length field enter the maximum number of digits to be read. If a fixed number is used the Padding field will not be operable. Step 4. In the Company section, the Start from and Length fields enable checking a preset card code. The Value field is for checking the Company Number (or Dept. Group, etc.) within the Card Number. Step 5. The Verification section is for verifying card data. In the Start from field fill in a number that signifies which digit to verify. In the Length field enter the number of digits to be verified. If in a particular company there are four departments (or four daughter-companies). Each department can be defined by a set of numbers (a value). These numbers will be added to the employee number. Thus, an Access Card can be comprised of two numbers; one assigned to the department, and one assigned to a particular access card. When Padding a number fill in the digit spaces required for a proper number (reader identifiable). Padding is necessary when a card number contains fewer digits than the total length defined in the Terminal Setup screen. Example: Access Card No. 300564798823XX Department ID no.

Individual Card no.

Padding

300564798823

300564798823XX

300564798823 XX

It is recommended to classify this code as a customer, not a department code. Every organization will be given a unicode shared by all departments.

36

Routine Operation


Additions

Permitted Tables Quantity- Is the number of access-permitted tables sent to the terminal. Firmware Waiting Timeout- The number of seconds from the last host request before giving a “No host” reply to the SAL. The terminal then reverts to offline mode and will revert to online mode only on the next host query. Used only for serial communication. The recommended waiting time is: 5 seconds. Automatic Data Send Freq.- Frequency of sending Data from terminal to host (Polling interval frequency for TCP/IP communication) in seconds. 0 = The terminal will not initiate data sending to host. Queries are not affected by this parameter and are sent immediately to the host. SAL Query Timeout- The number of seconds the SAL waits for a reply after sending a query to the host. The recommended waiting time is: 2 seconds. SAL Query Timeout x Query Retries should be less than Firmware Waiting Time. Query Retries- How many times the SAL will try to query the host. User Code- A user defined code that can be used to identify the terminal, depending on the application run on the terminal. Use Internal Buzzer- Determines whether the internal controller buzzer will be activated when an error occurs. Open door if memory is full - Click the Yes/No radio button. Emergency open- During an event determines how the SY-400 relays will react. Project Directory- This is the location of the terminal programming tables.

37

Routine Operation


Sensors As of firmware version 6.000 SY-400 has three sensors: the third sensor is used as a tamper switch. For older versions there are two sensors, sensor 2 is electrically connected to relay 2, therefore it will always be activated when sensor 2 is ON.

The sensors are managed as follows: 1. Definitions: Enabled- Enable/Disable the sensor Sensor debouncing- Waiting time for sensor to stabilize. Sensor monitoring time- Alert if the sensor has been active for longer than the defined time (activates the Sensor Monitoring Activities section below). Sensor type- Normally open (circuit is disconnected and the sensor shorts it) or Normally closed (circuit is shorted by default and the sensor disconnects it). 2. Sensor Initiated Activities: Save Transaction- Whether to create an event indication for sensor operation. Choose from the list box if the event will be written with the controller ID or one of the reader’s ID. Relay operation: Pulse, Disabled, Set, Reset Relay number- Enter either 1 or 2. If you wish to choose both, enter 0. Relay operating time- Time for relay activation in 1/5 seconds. LED buttons - Press a LED/s to operate when the sensor is active. 3. Sensor Monitoring Activities: Whether to save a transaction when the sensor remains active for more than the defined monitoring time (For example if the door was open longer than the defined time), and also saves a transaction when the sensor was closed after it was open for too long. Save Transaction- Whether to create an open-for-too-long/closed-after-open-too-long indication for sensor operation. If the selected Relay Operation mode is Set, upon closing the event, the relay will Reset (i.e.: to activate a buzzer when the door has been open for too long). Other parameters are identical to Sensor Initiated Activities.

38

Routine Operation


FPU FPU Mode SYServer- In FP verification: If there is a missing template: In Master mode, your terminal can send a query (using SY-Server) to get the missing template from the host. In Slave mode, the terminal will not query the PC for missing templates. Slave mode is the terminal’s default mode. FPU Security threshold- Here you define how strict the comparing of the fingerprint will be. Very High is very strict, Very Low is not so strict. Request FPU Status- When getting status from the terminal, it is requested to also get the fingerprint status from the FP unit.

5.3.4

Define an SY-400 Reader

In Setup, select Terminal List, and click the SY-400 folder tab. In the Reader List column on the right side of the screen there should be two readers. Define the readers as follows: Step 1. Click on Reader 1 and enter the Reader name. Step 2. In the Reader Type field choose the reader’s operational features from the drop down list. Note: Step 3.

Note: Step 4.

No authorized tables will be sent to a Disabled reader! In the Transaction Type field select the reader’s mode: None- Do not save transaction IN- Entry OUT- Exit Door- Define the transaction as Door Control- It will appear in the reports but not in the attendance reports. The card+keyboard readers combination can be used either as a card reader or number can be keyed-in. Choose an option from the Relay Operation drop-down list.

39

Routine Operation Step 5.


Step 8. Step 9.

In the Door Opening Time fill-in the time interval in which the door relay will be open.(1/5 sec). In the Relay Number field enter either 1 or 2. If you wish to choose both, enter a 0 into the field. In the Validation section at the bottom of the screen mark the options you wish to validate as follows: Company Check- A code (company/ dept. etc.) which is added to the basic card No. (As defined by the controller). Valid- The personal details in the authorized list. Note: No authorized tables will be sent to the reader if this checkbox is unmarked. Time Zone-The card is authorized for the specified time interval according to the specific time zone definitions. Local Anti-Pass-Back- Performs APB checks for specified cards between two readers pertaining to the same controller when one type is In, and other is Out. PIN Code-An additional security measure that requires an additional code insertion. A keyedin, 4 digit code. Auto mode selection will override it! Fingerprint- Can be assigned only to one reader. Must be marked in order to operate the fingerprint unit when using auto mode. Actual verification will be performed according to auto mode if selected! Host- Online verification using SY-Server and a special DLL (For example: FlconDLL.dll). Global Anti-Pass-Back- Performs system-wide APB checks via SYServer DLL. Auto Mode- Enables selecting of a preset auto mode. Click Save. To define a second reader repeat this procedure.

5.3.5

Define a COM-II-PRO Terminal

Step 1. Step 2. Step 3. Step 4. Step 5. Step 6.

In order to define a COM-II-PRO clock enter the Setup mode and click on Terminal List. Click on the COM-II-PRO folder tab. Click on New at the bottom of the screen; the Terminal Setup screen is displayed. At the top right fill-in the terminal name in the Name field. Click on the General, and enter the terminal ID in the ID field. In the Communication folder choose the appropriate connection type and fill in the rest of the fields as required. In the Cards tab define the position of the first digit of the card number and also the number length. In the Additions tab fill-in the number, place, and format of the Transaction files. At the bottom of the screen enter the PEP directory Name you wish to send to the terminal. Click either Save or Cancel.

Step 6. Step 7.

Step 7. Step 8. Step 9. Note:

Review the Falcpep sample project (under the Tables directory) in which the first transaction list (created by the terminal) should be in the format of: Card, date, time, key. The first permitted file should be in one of the following formats (refers to the authorized list content): Card- card only Card, alpha- card and name Card, alpha, alpha- card, name and ID.

You can assign various calculation categories to this terminal as per its function keys. For further information see 4.3 Calculation Groups, on page 25.

40

Routine Operation

5.3.6


Define an Alarm Controller (PRO version only)

The currently supported Rokonet ProSYS 128 is an alarm detection system that communicates with Falcon as follows: • Falcon can send PC date & time to the controller. • Transactions are collected via the Online screen only. Step 1. In order to define an alarm controller enter the Setup mode and click on Terminal List. Step 2. Click on the Alarm System folder tab. Step 3. Click on New at the bottom of the screen; the Terminal Setup- Alarm Controller screen is displayed. Step 4. At the top right fill-in the terminal name in the Name field. Step 5. Enter the terminal ID in the ID field. Step 6. Select the type/model of the alarm controller. Step 7. In the Communication folder choose the appropriate connection type and fill in the rest of the fields as required. Step 8. You must disable the RS-232 port FIFO buffering. Else Falcon will not be able to communicate with the controller: In Windows 2000: My computer | Manage | Device Manager | Ports | Communication port COM X | Properties | Port Settings | Advanced In Windows NT: Controller Panel | Ports | COM X | Settings | Advanced In Windows 95: My computer | Properties | Device Manager | Ports | Communication port COM X | Properties | Port Settings | Advanced

5.3.7

Define an Alarm Detector


Enter into Setup mode and click on Terminal List. Click on the Alarm System tab. On the Detector list screen click New; the Alarm Detector Setup screen is displayed. Fill-in an ID and Name. The Name of your choice to represent the detector location.

5.4

Define a Time zone

The Time zone module controls and defines the time-ranges of Master and SY-400 terminals access control per day type as follows:

5.4.1

Define a Time Zone for a Master Terminal

The Master terminal can define upto 15 Time Zones per Access (99 different Time Zones per Master unit), with or without use of the Calendar. To choose or cancel the calendar function enter the Terminal List folder. Click on the Additions tab and then choose With Calendar or Without Calendar. Step 1. After entering Setup click on the Time Zone Module in the Module list on the left side of the screen. Step 2. Click on the TZ Master tab. Step 3. To add a new Access Group click on the New button at the bottom of the Time Zone List; a new line is added to the Time Zone List column, fill-in the appropriate name. Step 4. Click the Edit button, the Edit Time Zone screen appears. Fill-in the fields with all of the pertinent information - time and date ranges for particular days of the week. Under Access mark the relevant radio button to either grant or block access for the marked days. Note:

Similar to Auto Mode when the calendar is used each space represents a Day Type, while without the calendar, each space represents a day of the week.

41

Routine Operation


When marking the Yes radio button in the Use Calendar section in the Terminal setup screen, only one day type (each of the numbers 1-7 represents a day type) must be marked by a +. (number 1 in the example below). From Time

To Time From Date

To Date

1 2

3

4

5

6

7

Pass

6:00

18:00

7/1/02

+ -

-

-

-

-

-

+

1/1/02

When marking the No radio button in the Use Calendar section in the Terminal setup screen, only one day type. In this case each number will represent a day of the week, thus all regular days must be marked by a +: From Time

To Time From Date

To Date 1

2

3

4

5

6

7

Pass

6:00

18:00

7/1/02

+

+

+

+

+

-

+

5.4.2

1/1/02

-

Define a Time Zone for SY-400

Unlike the Master (you can either use or not use the calendar for time zone definitions), SY-400 time zone definition requires setting the calendar parameters. Step 1. Click on the SY-400 tab. Step 2. To add a new Time Zone click on the New button; a new line is added to the Time Zone List column, fill-in the appropriate name. Step 3. In the Time Zone chart, by clicking and dragging the mouse, mark the days and hours you wish to define. The chart is comprised of 30 minute time units (right-clicking enables tweaking to 15 minutes units if required). Mark the Edit check box, and make sure that you are in the correct mode (allow and disallow). Note:

While surfing the mouse across the chart, you can see its exact location indicated at the bottom of the chart (day type and hour).

Note:

The Allow/disallow options enable changing the colour. (This was previously done in the Options screen).

42

Routine Operation

5.5


Define a Security Group

SY-400 For SY-400 terminals it is possible to assign upto 5 different security groups per employee. The expire date is checked only when the tables are sent. Only groups that have not expired are used. Master Master can hold one record per employee with one expire date. When two security groups refer to the same Master terminal the software will choose the most proximate valid expiry date. Time zones will be matched as follows: For each reader (Access) an internal list of all active time zones is created. If no active time zone exists for this employee for this reader, then, access will be denied. Else, the time zone with the lowest ID (the Master Time Zone list is sorted by ascending time zone ID) will be used. This module enables assigning a security group to a Time Zone and a door: Step 1. In the Security Group screen, click New and enter a name for the new security group. Step 2. Define a permission level for this security group. The permission level must coincide with the the relevant supervising operator permission level (for further information see Chapter 12 Maintenance, on page 65 - Users). Step 3. On the right side of the screen under Security Group Details click Edit or double click your mouse on the Security Group Details side of the screen. Step 4. The Edit Security Group screen will appear. All defined readers will be listed on the left. Next you will find a table that enables assigning a time zone to a reader. On the right a list of the currently defined time zones. This screen enables dragging and dropping data inbetween lists. Note:

By right-clicking on a group it is possible to copy the group contents definitions to another group (again right-click and paste).

Note:

Inactive readers will not appear in the available readers list.

43

Routine Operation

5.6


Define an Employee

The Personnel file enables reviewing all employee general information according to different sorting. This database can be updated at any given time. Note:

Data can be inserted directly on the grid only when the Allow Grid Edit check box is marked.

A new employee can be added as follows: Step 1. Click Personnel, New; the Employee details screen appears. Step 2. Leaf through the Management, General, and Details tabs and fill in the relevant information. Note: Step 3. Step 4. Step 5.

After entering the photo file name, the photograph appears in the personnel screen. Click Send Last if you wish to update the system with the particulars of one card-holder Click Send All if you wish to send more than one. Mark either of the radio buttons representing options for sorting per your choice.

Note:

You can refresh your screen using the F5 button.

Note:

When using the Find option an incremental search is activated.

For elaborate information on employee management, see Chapter 4 - Personnel, on page 21.

44

Communication


Chapter 6 - Communication This feature enables the user to communicate with the terminals in order to send or receive various information. Firstly you must choose the relevant controller/s (unmark the Send to All tab). The Send tab transfers data to the controller. While the Receive tab transfers data from the controller to the computer (Status, new transactions, old trans, authorized list) and determines what data will be received and the source’s location.

6.1

Sending data to terminal

Step 1. Step 2.

Click the Send tab. Select All Terminals or a specific terminal. Select which data type will be sent. The following data can be sent: Field

Description

Time and Date

Sets a new date and time in the terminals.

Configuration

Sends the settings defined in the Terminal List.

Security Group (Not applicable for Com-II-PRO)

Sends all defined settings in the following folders: Security Groups, Time Zones, auto mode, Calendar

Permitted Cards

Sends the settings defined in the Personnel folder.

All Templates (SY-400 only)

When unmarked: Only new fingerprint templates are sent to the terminal. When marked: The terminal fingerprint template memory is cleared and all authorized templates stored in PC are sent to the terminal.

Note:

For SY-400: the authorised list will include employees that did not enrol an FP template (can be enrolled retroactively and sent to the terminal individually). 45

Communication


Reset a terminal (Master only) This operation initializes the terminal and will cause all transaction data (including those that were not collected) to be permanently lost: Select Send To All or a specific terminal. Click Reset. Browse file Enables viewing LOG files.

6.2

Retrieving data from terminal

Step 1. Step 2.

Click the Receive tab. Select Send to All or a specific terminal. Select the type of data to be received.

Field

Description

Status

Opens a window containing a display of the status of the terminal(s) and attached readers.

Transactions

Collects new transactions from the terminal(s). Transaction data can be viewed in the Transaction table of the Online module.

Old Transactions

Recollecting of old collected transactions from the terminal(s) along with any new transaction.

Permitted (Master Only)

Displays a list of all cards currently stored in the terminal’s memory.

Faulty records will be registered in the Rejected.nnn (n=terminal number) file. If the transaction file is faulty and data can not be registered on it, data collection will stop. Under the Receive tab you will find the number of rejected records.

46

Events


Chapter 7 - Events In addition to regular transactions, the Falcon software also enables retrospective investigation of special transactions such as: Card no longer valid (expired), access not permitted, etc. These special transactions, called events, can be outlined by sound and colour, and be sorted out accordingly. Creating A New Event Click on the New Event button. Define all of the Event fields. Editing An Event Line Select the event and click Edit or, double clicking on an event line enables editing. Note:

You can mark the different events in different colors.

Delete An Event Select the Event line. Click on the Delete Event button. The event definition screen is comprised of 4 tabs: General- Initiating the event, and typifying it. Indication- Marking it by color and sound. Automatic activity- Informing an external/internal party about the event via SMS, See “SMS (PRO version only)” on page 16. Operator instructions- Upon occurrence of event, instructions to the operator. The Pass event type refers to all valid transactions. All transaction types other than Pass can be classified as All Exceptions or require a specific definition. Event management All current events are displayed in the Online screen. Double clicking one of the rows will display the Event notification screen. General Field

Description

Description Event type Active Card range Operator response time Save event in the Open Events file

A free text field in which the user can characterize the event. An irregular transaction type. An event can be active = functional or when this check box is unmarked = not active. The event will be relevant for a defined group of card holders. If within the preset time the operator does not respond it will be indicated in the system. Unmarked by default. If marked, this event type will be saved in the Open Events file and displayed in the Maps screen.

Indication Field

Description

Presentation color Sound Popup Message

You can attribute a specific color to the event. You can attribute a specific sound to the event. A popup message that will appear on the terminal display upon event occurrence.

47

Events


Automatic activity Send SMS: During an event it is possible to send an indication SMS message to a mobile phone subscriber list. For further details See “SMS (PRO version only)” on page 16. Operator instructions Enables free text writing of instructions to the event operator.

48

Message Translation


Chapter 8 - Message Translation Falcon enables interface language changes to a destination language of the user's choosing. This procedure is usually performed by the dealer yet can be undertaken by the user without difficulty. Falcon can store upto three different languages within the system. One in use, and two "on-call”. The translation process is a combined one, it is done within the software and using a utility. First begin translation within Falcon, then using the utility as per the explanation below. There are three kinds of captions to be translated: Heading Message

Hint Within Falcon you must: Step 1. Step 2. Step 3. Note:

Go to Setup | General Parameters | System | Localize make sure the Language is English. Revert to Setup and choose the Message Translation module. The screen (see page below) is divided into two parts. The upper part consists of the current System Messages and the lower consists of Words and Headings. To create a list of all the text in the system click Import. This will fill the messages table (which is empty by default) with the latest English text from the current EXE. To make sure you import the most updated exe wording, you must go to General Parameter | System and change the Language to English, then Restart the program.

Your screen will now look like this:

49

Message Translation


The column titles signify as follows: English, English HintLanguage RTL (caption text), Language RTL Hint (hint text)Language LTR (caption text), Language LTR Hint (hint text)-

is designated for the English language text is designated for Right-to-left writing direction languages (Hebrew/ Arabic). is designated for left-to-right writing direction languages.

Step 4. Step 5. Step 6. Step 7. Step 8. Step 9.

Translate the text!! In Setup | Calendar | Customize, update the name of the days. Exit Falcon and run FaLang.exe. Translate all the LU files. Exit FaLang. Once all necessary files (see Foreign Languages, on page 80) were translated you can send them to our customer support department to prepare a new localized set. To choose a particular language that has been translated: 1. Go to Setup | General Parameters | System | Localize and change the language to Other (if you want your Language to replace the wording: “Other”, go to Message Translation, PosID 3576 for LTR languages and PosID 3574 for RTL languages, and fill-in your Language name). 2. If required, change also the direction. Using the Utility: Step 1.

Some of the utility tables must be translated using the FaLang.exe program. In your installation CD, go to Utility and copy the FaLang.exe to the PC where Falcon is installed and run it. You have a list of tables to select from, each one contains English text. Overwrite this text with your appropriate text. Step 2. You should restart Falcon in order for this data to be fully integrated. For further details refer to “Appendix B - Database”. Bottom screen buttons: The Find button enables locating a word from the current location (Find Next) F3 performs the search from the last word. A partial search is also available (the beginning of a word). The Empty button at the bottom of the screen clears the lower screen of all translated text (thus clears all message file content!). The Report button enables printing the message list for translation purposes. RECOMMENDATION: YOU SHOULD REVIEW THE SCREENS TO MAKE SURE THE TEXT FITS AND THE MEANING ACCURATE!

50

Reports


Chapter 9 - Reports Falcon consists of the following standard reports that can be selected from the Reports menu on the Falcon menu: • • • • • • • • • • • • • • •

Online Presence/Absence (you can click on the Presence Report icon instead) Transactions (you can click on the report’s icon instead) Visitors Events: Open, response time, old Entries System (you can click on the System icon instead) Personnel Security Group Readers per Security Group Access Readers Time Zones Duplicates: Cards, Names, IDs, Photos Generator Custom Report Additionals: Expire Dates, Cards Issued, Active Personnel for TimeLOG Fire (Emergency menu)

These reports can be saved in TXT, CSV (Excel) or HTML formats. Tips

:

1.

Right-clicking your mouse on a report line in the result screen to Edit Employee.

2.

In the same screen you can define CSV parameters:

51

Reports

9.1


Presence/Absence Report

Choose Presence or Absence and then press Run. You can Preview or Print the report. The Presence report is generated from the active personnel list (similar to the fire report, see Chapter 13 - Location, on page 67). The absence report provides a list of the current absent employee list as per the specified sorting. If the Write Last Transaction into Personnel File check box is marked, then the report will show employees’ corresponding last transaction (see 3.3.2 System Settings, on page 10). The report can be generated for 0 days (today) upto 99 days retroactively.

9.2

Transaction report

This module enables issuing reports per transactions. It enables issuing transaction reports according to different categories: date, time, card, security group (display of all assigned security groups), department, employee ID number ranges, employee names, population types (regular, visitor, guard) and event type. It is divided into 3 tab screens:

9.2.1

General

This report is divided into 5 sub-reports. For all these report types data can be generated for an old transaction file. All other report components (such as: personnel and terminals) will be taken from the current database (in order to avoid incompatibility of record format etc.). For no longer valid personnel no name indication will appear. Mark the Generate report from history data check box in order to use this feature. Transaction List This report includes events and row transactions, and can be generated for old as well as current transactions. These can be sorted primary and secondary sorting.

52

Reports


The four following reports are different entry-exit summaries and exclude event transactions: Attendance with Totals This report pairs legal entry and exit transactions, and disregards illegal transactions. It calculates totals per day, per employee, per department and an overall total.

It enables sorting these transactions by: card number, employee name+card number, and department+employee name.

53

Reports


Pressing the Adjust button opens the following screen:

It enables setting user definitions for daily totalling, and enables determining how totals will be calculated. In the absence section you can include absence data in the report. The First IN and last OUT of each day radio button, enables display of only the 1st legal transaction for that work day and the last legal transaction of the same day. Note:

Unless you mark day types to be included, absence data will not be displayed (although the check box is marked!).

Day Count per Person A statistical report counting for each person the number of days he reported during a specified period. Swipe Count per Person This report counts the number of valid swipes per a specified period as per the different transaction types. This report can be sorted by: card number, employee name+card number, and department+employee name. Note:

Under Employee Details | Management | Expected Swipes, you can define a reporting limit for that employee.

If you mark the Exceptions check box, only a total that does not match the totals different than the total indicated in the Expected Swipes field will be indicated. Note:

Make sure that the total specified under the Expected Swipes field is for a period that matches the period specified in your report!

Person Count per Day This report counts how many people reported during one day.

9.2.2

Reader/Security Group/Calculation Group/Population Selection

By default all readers/Security Groups/Calculation Groups/Populations are included in the report. If you want only specific information to be included mark it and click on the > symbol. To remove all items that were selected, click on the << symbol. To remove a specific item, select it in the right column and click on the < symbol. Click Run; the relevant information will appear on the Transaction report screen. Note:

The report parameters: Date, time and card are processed substantially faster than sec. group, department, ID and name, which are going to slow down the issuing of the report if selected.

54

Reports

9.3


Visitors

This module enables issuing reports per visitor transactions. It enables issuing a report according to different range categories: Date, Time, Last Name, Person ID, Company, Host name, Department, Event types (regular, visitor, guard). It is divided into 2 tab screens:

9.3.1

General

The procedure for issuing a report is as follows: Step 1. Click Reports in the main menu, and then Visitors. Step 2. To generate a report define the above mentioned parameters and the preferred sorting. Step 3. After entering the information in the fields click Run.

9.3.2

Readers

By default all readers are included in the report. If you want only specific readers to be included mark it and click on the > symbol. To remove all readers that were selected, click on the << symbol. To remove a specific unit, select it in the right column and click on the < symbol.

9.4

Events

There are 3 different event reports: Open events- A time range report of events that were not yet attended to. Response time- Indicates frequency of reaction of the operator to events. (The time interval between event initiation and operator response). Old events- A time range report of closed events.

9.5

Entries

This report displays all legal transactions and is designated for exporting data to TimeLOG. Each entry and exit displayed in a separate record. The report can be filtered by employee name, department and population. 55

Reports


The Data Selection section offers two possibilities: • Display the first Entry and last Exit of an employee for the specified period. • Display the first transaction and the last transaction of an employee for the specified period. This report can be exported to an ASCII file as per user specifications. See Export transaction screen below:

This report filters access control transactions for attendance control purposes. The file’s potential components are listed. You can prioritize the list and you must check the items to be included in your export file. Outlined in the screen above is an export file to TimeLOG.

9.6

System

The system report details individuals who have access to each door and outlines their access restrictions. To generate a System report: Open the System Report, select the relevant terminals and click Go.

56

Reports


An extended filtering per card/name/department ranges and various sorting facilitate employee access management. It is possible to print, preview or export this report to HTML.

9.7

Personnel Security Group

Lists all the people that belong to a group.

9.8

Readers per Security Group

A fixed report showing security group allocation information.

57

Reports

9.9


Access Readers Time Zones

A fixed report showing security group allocation information including time zone data (enables comparing between time zones and between security groups).

9.10

Duplicates

9.10.1 Duplicate Cards All employee cards that were indicated more than once in the Personnel file. Note:

By default this report should be empty! If not, this signifies an error that must be rectified!

9.10.2 Duplicate names All employee names that were indicated more than once in the Personnel file.

9.10.3 Duplicate IDs All employee ID numbers that are indicated more than once in the Personnel file.

9.10.4 Duplicate Photos All employee photos that were indicated more than once in the Personnel file.

9.11

Generator

There are several possible ways of printing reports of cross-sections transactions per employee or per a group of employees. The reports are generated from built-in templates that can be user-generated/created. When the user saves a customized report a sub-menu will be added to the Customized report menu.

Generating a report Step 1. In the Report Generator screen click on the Select Table button and select a Paradox table. Step 2. Click on the >> button to place all fields in the Report, or select a field from the Field List and click the > button. Step 3. Enter the relevant ranges for each field, and define the sorting priority by double clicking the relevant field (A priority choice can be unmarked by double clicking a second time).

58

Reports


Step 4.

Click on the Go button to generate a report and on the Preview button to view the report on screen. Step 5. In order to print the report, click on the Print button. Creating a report template When saved, these new report templates are automatically stored under Reports | Customized Report for future use.

9.12

Custom Report

All reports that were issued via the report generator are stored here for future use.

9.13

Additionals

9.13.1 Expire date A list of all expired cards.

9.13.2 Card Issued A list of the last issue dates of cards that were printed (Print card button for PRO version only) during a specified period.

9.13.3 Active Personnel for TimeLOG

This report is designated for exporting Falcon active employee database to TimeLOG, filtered or not as per user preferences. It can also be sorted by: ID, First/Last name and card. Two sections determine where to insert the source data field at the TimeLOG destination field: • Falcon Field used for TimeLOG Employee Number: whether to present the ID Number field or the Card Number source fields under TimeLOG’s Employee Number destination field. • Inform TimeLOG of the order of the employee full name: what comes first: the last name or the first name (In Falcon both are under one field, in TimeLOG they are under two separate fields).

59

Working Online


Chapter 10 - Working Online Supported only by a local or by TCP/IP communication Master or SY-400 terminals (not COM-II-PRO or MODEM – for these terminals the frequency of data collection can be defined in Options | Automatic scheduling | Collect data). This module displays an online table of current data as it was collected from the terminals. The photo on the left side of the screen is of the last card-holder transaction. As transactions are collected the pictures change accordingly, and the statistics are updated. The active/inactive status of the communication link is displayed. There is a filtering option to display all/non event/event transactions. Also, right-clicking on a row allows the user to edit the employee’s details screen.

5 6

1

2

3

4

7 Field name

Description

1

Auto Refresh

Starts refreshing the screen, skips to the last line on a predetermined frequency (see 3.4.1. Options, on page 12). There is no communication with terminals, and this activity is designed to show new data that was collected by another workstation (collect data PC) or another software (SY-Server).

2

Start Scan

Begins data collection (polling) from all active terminals.

3

Stop Scan

Terminates Start Scan or Auto Refresh.

4

Show image Displays details and a large sizable picture of the last transaction that was collected, enabling filtering by the reader. A video display (PRO version only) can popup so that the operator can compare it with the database saved picture. This feature is enabled only when the Auto Refresh or Start-scan are active.

5

Double-clicking on this screen displays the Event notification screen (see Chapter 7 -. Events, on page 47 and see 10.1. Online event management, on page 61).

60

Working Online

6


Field name

Description

Statistics displayed

Name

The name of the terminal unit sending it's data. (Defined in the Terminal List).

Master ID

The ID of the terminal unit (Defined in the Terminal List).

Record number

The currently selected data record.

Total number

The total number of online data records.

7

Indication of an activity in progress.

Show Image screen

10.1

Online event management

Event management is carried out via the Event notification screen in the Online folder. Controlling events is implemented by tracking event occurrence and quickly taking action (operator). Event status, comments and instructions can be updated online.

61

Working Online

Note:

10.2


To speed up the procedure use the F7/F8 keys which will: mark an event as either Investigated/ Closed, save and exit the screen.

Clear the online table

In order to delete data from the online database: Step 1. Click on Maintenance in the main menu and then on Clear transactions. Step 2. Choose the Date field, then choose a date by which to delete all transactions from the Online Table display. These transactions are PERMANENTLY deleted from the Transaction file. It is recommended to perform back-up before deleting data from the online database. Note:

If there are many transactions in the table (20,000 or above), it could take a few minutes to clear the data, please be patient.

62

Visitors


Chapter 11 - Visitors Visitors are an integral part of enterprises’ daily activity. Falcon has the capacity to provide any number of visitors with access cards easily monitored and managed.

11.1

Creating cards via Personnel

Under Personnel all cards are set-up. For visitors, which is a unique case of cards, you must first create here a new line here consisting of a Card Number, Name and choose Visitor as the Population Type.

11.2

Handling visitors

Adding a new visitor Step 1. Click on Visitor; the Visitor List screen appears. Step 2. Click on New; the Visitor Details screen is displayed (below). Fill-in the particulars and assign him/her to a Security Group.

Step 3.

Click Set Host to assign a host to your visitor (from Personnel screen). The host is an employee who is responsible for handling visitor affairs within the organization. Step 4. To issue a card you can either click the Issue Card button and fill-in the number that was defined in Personnel, or use a keyboard emulator reader to read the number from the card itself. Step 5. Click Save; the new particulars are listed in the Visitors List screen . Step 6. Choose also a card layout. To create a new card layout see paragraph 3.4.3: "Edit Card Layout (PRO version only)", on page 18, (you can also print the card using the Print Card button). If required, you can add a transaction manually for this visitor. This may be done after card assignment, to mark that the time point on which the visitor has been assigned the specific card.

63

Visitors


Return Card To check a visitor out of your organization’s facilities do either: • On the same screen click the Return Card button. • In the Visitors’ main screen click Return Card, fill-in the card number and click Yes. Now the visitor is no longer permitted access to your offices. His entries and exits have been recorded in the system. Visitor transactions are registered under the visitor’s name. for further information refer to the Reports chapter, paragraph 9.3: "Visitors", on page 55. Note:

While issuing/returning the card, the visitor is automatically transmitted to all currently/ previously authorized Master terminals.

Note:

The FIND option activates an incremental search.

Note:

Multiple visitor rows can be high-lightened (by holding Shift+Arrow) and by pressing Ctrl+Delete the user can delete all marked visitors.

Note:

You will not be able to delete a visitor unless you receive his/her card and click the Return Card button accordingly.

64

Maintenance


Chapter 12 - Maintenance This module consists of eight menu items that allow you to perform a variety of standard maintenance activities. Collect Data- Collects new transaction from all active terminals. Send All Data- Reprograms all active terminals to reflect changes in the system. Send Updates- Sends recent updates and new fingerprint templates from the authorized list to all active Master or SY-400 terminals. Users- Enables defining a system operator’s security level by restricting access to Falcon modules accordingly. Access to a module is allowed by marking the check box. Note the variety of editing options for the Personnel and Visitor screens (Add, Delete, Modify Group, etc.) Another means of operator restriction is the permission level which is determined when defining a new user or editing a user. Herein you must fill-in the system operator’s user name, password, and permission level. The maximal permission level value is 9. Currently this leveling is implemented for security groups only. This means that a user can assign a security group only if its ranked permission level is lower or equal to his. For further information see paragraph 5.5 Define a Security Group, on page 43. Once a system operator with access to Users is defined, a password must be inserted in order to start Falcon. Pay attention: A supervisor must be defined as instructed. Make sure that that at least one supervisor is defined at any given time. Otherwise new users can not be added!

65

Maintenance


Backup- Saves a database file in a ZIP format for future use. To create a backup in a ZIP format, click on Backup, give a name to the new file and click Save. Note:

Falcon.ini is also backed-up (technical support can detect parameter definition originated problems in this file).As a precaution, this file does not open during the restoring procedure.

Restore- The directory restored will be saved under the same name and under the same directory (without the ZIP extension). Restoring houses two functions: 1.

Files Restore- Retrieves a zipped database file and saves it as such in the directory. After retrieving the database file you can reload it into the system as a working database file. To do this choose Alias to Restore (under Restore).

2.

Alias to Restore- Enables database reference change for restoring purposes, without re-placing the files. Click on Alias to Restore; the file directory opens. Choose the required directory. Falcon will close automatically in order to update the definition changes. Then, Restart the program.

Note:

Do not collect data while working with restored data. Revert to your currently used folder only after restored data has been handled.

Note:

Before back-up and restore operation on a specific work-station, Falcon will signal all other work-stations that their database will be shut-down for 90 seconds. Make sure that the Event Signalling Frequency field (under Tools| Options| Online) has a value larger than zero!

ReIndex- Re-organizes the database when a file corruption occurs in the index files. For further information see see paragraph ReIndex.exe, on page 83. Note:

During installation a shortcut is created (Start | Programs | Falcon). It activates Reindex /Repair to help clients with the repair procedure.

Clear transaction- Omits all transaction types (transaction, open/closed events) on a daily basis (see paragraph Chapter 10 - Working Online, on page 60). Synchronize fingerprint- For further information refer to see paragraph 15.3 Synchronizing Templates, on page 74.

66

Location


Chapter 13 - Location Enables updating of terminal data, rendering system maintenance quicker and simpler. To update and view terminal data without entering the Setup screen: Step 1. Enter the Location screen. Click on the Location button. Step 2. Mark the particular terminal and then right-click. Click on edit from the pop-up menu. The relevant Terminal Setup screen will displayed. Fill-in the various fields in the four tabs and continue as indicated in the Set-up folder. A right click on a terminal/reader opens a content sensitive menu enabling live video view (PRO version only) and door control, as follows: Properties-

Opens the terminal/reader set-up screen where you can change camera definitions+access control definitions. CCTV Live ViewEnables activating the camera connected to this terminal/reader. CCTV Disconnect Site- Disconnects the camera connection. Open DoorEnables keeping the door open constantly. Lock DoorEnables keeping the door closed constantly. Door to NormalEnables reverting the door to its default relay mode.

13.1

Emergency

13.1.1 Generate a Fire (emergency) Report Displays real-time attendance data of employees and visitors that are within the facility. Similar to the Presence report yet prior to issuing of this report the software collects data from all active terminals. Note:

The following definitions will be determined via the Presence report (can not be defined under the Fire report settings): Sort By Insert Page Breaks Number of Days Retroactively Transaction Type

13.1.2 Door control Enables management of all reader controlled points of entry in an emergency: opening/locking all doors, reverting doors to normal or controlling each door manually (Door control). Also, changes in door mode are represented graphically (red/green LED) under Location.

67

Location


Under Door Control you can change the relay mode per reader:

Open All DoorsLock All DoorsDoors to NormalNote:

Enables keeping all doors open constantly. Enables keeping all doors closed constantly. Enables reverting all doors to their default relay mode.

Emergency settings override reader default door monitoring definition.

68

Maps


Chapter 14 - Maps The maps feature is designed to display visually event notifications on a map of the organization’s access control hardware devices. Upon entering this screen Falcon synchronizes controller and reader status into the Map module. Then the operator can detect online the exact location of the event. The maps can be presented hierarchically and enable zooming to smaller areas. Maps can be edited in the designated Edit Maps screen. The View Map screen enables operators to spot and handle events on-site. As a precaution, if more than a 100 events remain open (not handled), the last 100 updated events remain open and the others are stored in the closed events folder classified as automatically closed. Simultaneously, an alert message appears notifying the operator that 100 events were not handled. Edit site Step 1. Click on the Tools drop down menu and then on Edit site. The Edit site screen will appear displaying all currently installed access control devices. Step 2. By right clicking you can add a new terminal/reader/ or any new hardware devices.

Step 3. Note:

Please note that the icons are piled up, so in order to see all icons you must drag and drop them over the map. Falcon does not include an option to draw maps or scan a map, therefore maps must be drawn in Windows standard tools and import the map as a JPG or BMP file.

Step 4.

To add a background drawing of your premises click the Properties icon and browse to find the BMP or JPG file:

Step 5.

In order to create a new map, place the cursor on the map tree and right click. Click Add new map:

69

Maps


Name the map. You can add a sub-map under an existing map. You can also drag and drop icons from map to map. Step 6. Changing terminals/readers positioning is done by dragging the relevant device to the required map. View site (Main tool bar) The Falcon can display event indication and location online (Automatically refresh). Given, of course, that data has been collected. • Enables viewing your premises map and current events simultaneously. • Each Event is highlighted chronologically and the equivalent terminal is framed red. • Devices that are not active (the Active check box, in the General tab in the Terminal setup screen is unmarked) are marked by a red diagonal line. If there is an event pertaining to a terminal which is not currently displayed, the relevant map icon will be framed red. • Double clicking a map induces map display. • Double clicking a terminal induces highlighting of the highest level open event. • When right clicking a controller icon the Terminal setup screen will appear. This enable adjusting setup parameters. • When right clicking a reader icon this content menu appears:

Properties- Reader setup screen enabling adjustment of setup parameters Transaction report- Enables posing a query, (see Chapter 7 - Events, on page 47). Authorized list- A list of all approved cards for the specific reader. Open event- Enables posing a query, see Chapter 7 - Events, on page 47.

70

Fingerprint


Chapter 15 - Fingerprint Note:

Older firmwares support the MV-1200 unit with a 6 digit ID. See table below for specified firmware variations: Firmware version 5.115, 6.101 + 6.200 8.032x 8.033x

Fingerprint Unit Type MV1200 MV1200 MV1200 FPU-S

No. of ID digits 7-8 9-10 10 10

The basic biometric concepts are: Enrolment Scanning a fingerprint, determining quality of the scan and storing a good template as a reference. Enrolment is confirmed and scanning quality data is outlined. Scanning quality is a by-product of the skin’s condition: dry skin can contribute to an unreliable image. A normal amount of moisture on the skin makes the ridges and valleys of the fingerprint stand out to the sensor. Too little moisture makes the image “noisy” and causes the enrollment unit to reject the image during processing. Lightly moisturizing the finger will enhance the contrast of the print and provide a more reliable verification. An increased sensitivity of the silicon sensor can dramatically reduce such problems. Identification Does not require a card/code. Fingerprint templates are stored in the terminal’s memory. Whenever an employee places his finger on the sensor, the Fingerprint (FP) unit scans all existing templates until there is a match and confirms/rejects. Verification Requires a card/code. The template is stored in reference to a card/code. Card/codes and templates are stored. When an employee swipes his card/keys-in his code, the unit checks if the card/code number exists, if it does it checks also the template assigned to that number. All unit can perform enrollement via your terminal. Whereas, each unit offers different features and ranges as follows: Quality The quality score is based on how well the ridge pattern is defined within the fingerprint image that was enrolled. Quality measures how clearly the unit imaged the fingerprint. Poor quality enrolment can result in an elevated rate of false rejection making it difficult for the user to verify reliably. The score ranges from 0 to 100. A 100 is the best quality (rarely obtained) and 0 the worst. Quality scores of 40 and higher perform well with the verification algorithm that readily compensates for differences in fingerprint. Content The Content score is based on the amount of usable information the unit sees in the fingerprint. Templates that are characterized by low content scores may result in elevated rates of false acceptance. The score ranges from 0 to 100. A 100 is the maximal content and 0 the minimal value. Content scores of 20 and higher perform well with the enrollment device. In this range the algorithm has enough information to distinguish between different fingerprints with a high level of accuracy. Templates with content scores above 20 do not vary in terms of the error rates.

71

Fingerprint

No. Templates in Terminal 4000 Verification 200 Identification 1000-9000 FPU-S * **

15.1


Templates per employee* 10 10 1

Save on Mifare card** + +

PC Enrollment PRintX PRintX PRintX or USB reader

PC enrolment allows up to ten templates per employee (two templates in the Express version). Terminal enrolment allows up to two templates per employee. When saving a template to a Mifare card, only one template per person can be used.

Hardware

The required hardware is as follows: Compatible Terminals SY-400 or SY-780/A Compatible Reading Units • PRintX/H (serial) or FP-S200/FP-S300 (USB) • Mifare reader/writer (Possibility to save template on card)

15.1.1 SY-400 Definitions Terminals For set-up instructions see paragraph 5.3.3: "Define an SY-400 Terminal", on page 35. Readers To enable fingerprint verification for an SY-400 reader: Under the Terminal list folder, choose SY-400. In the reader to be connected mark the Fingerprint check box. To enable fingerprint identification for an SY-400 reader: Step 1. Under the Terminal list folder, choose SY-400. In the reader to be connected mark the Fingerprint check box. Step 2. On the same screen choose the following Reader Type: Fingerprint Auto-Identification 10 digits (must be implemented on Reader-1 only!) Note:

15.2

For SY-400 terminals, only one fingerprint unit can be connected to one of its two readers.

Software

15.2.1 System Options For information on systematic fingerprint definitions see paragraph 3.3.2: "System Settings", on page 10.

72

Fingerprint


15.2.2 Local Options Under Tools | Options | Fingerprint you can set-up enrolment unit communication parameters as follows:


You should select the directory that is going to be used for storing fingerprint templates (in a multi-user environment it should be placed on a shared directory). Select the FP reader that is connected to this PC. For a serial reader, you should define the Port (it is recommended to use a port that is not used for communication purposes, otherwise the user will be forced to manually switch cables), Baud rate (57600 default rate).

Saving to the Mifare Card Falcon supports two types of smart contactless cards: Mifare-1KB and Mifare-4KB. Fingerprints can be saved on these cards in a secured way, using the Mifare reader/writer unit. When the Save Fingerprint Template on Mifare Card check box is marked, enrolled templates will be saved on the card (with an option to save an additional copy to the disk). Verification then, will be performed from the card itself only.

15.2.3 Employee Activities

73

Fingerprint


Enroll Enrolling is performed as follows: Note: Step 1. Step 2. Step 3. Step 4. Step 5. Step 6. Step 7.

For units other than FPU-S you can enrol and verify regardless of the unit type: verification or identification. In the Personnel screen mark the relevant employee row. Click on the Finger button. Click Enrol in the Fingerprint screen. A message instructing you to place your finger appears. Place your finger on the device. A Remove finger message appears. A fingerprint scan score is displayed (See quality, content at the beginning of this chapter). In case the user wants to re-scan he must click No and revert to the Fingerprint screen. If the user wants to confirm, he clicks OK. When enrolling on Mifare cards: You will be asked to place your card proximate to save the template from the reader to the card. Repeat steps 1-6 for each template.

Step 8. Verify Compares the saved template with the finger currently placed on the unit. Send An employee’s template file can be sent from the PC to all authorized terminals. Download Choose the relevant terminal, then download the required templates from that terminal. Downloading will be performed for the highlightened employee (line). Designated for: • Enrolment from the terminal and not from the PC. • Backup- If the template was lost in the PC you can restore it from the terminal. Note:

The program registers all templates that were sent to a terminal. Then, during programming matches templates and sends only templates that were not sent. It is possible to send all templates via the Communication screen.

Remove An employee’s template file can be removed from the PC to all authorized terminals (not from PC).

15.3

Synchronizing Templates

Under Maintenance menu click on Synchronize Fingerprint Templates. This will make Falcon synchronize the fingerprint directory: Tools| Options| Fingerprint| Template directory with Falcon’s Personnel file: Falcon scans the employee file and marks for each employee if there is a matching template file. This allows importing fingerprint templates from an external program and cross-matching those with an employee list.

74

Terminology


Chapter 16 - Terminology Anti-Pass Back- Prevents multiple access of one card by conditioning it with swiping a second reader in a different location. Auto Mode- An operation option for the reader that enables changing working modes automatically according to the specified Time Zone. These modes are for example: card only, or card and PIN. Camera site- A device or PC that is used as a server for several cameras. Day Type- When the Use Calendar option is active, you can define a day type: full, half working day, vacation etc (up to 9). Duress Code- A code used by a user threatened by an outsider. After keying-in this code the door is opened and simultaneously an event is sent to the host computer. Used by Access reader in Card+PIN mode. Employee ID- A personal ID number of an employee. Expiry Date- The last validity date of a card. Event- An irregular access violation registered and displayed in the Online screen. Enrol- When using the fingerprint feature employee fingerprints are sampled: The employee places his finger on the reader, and the sensor scans the finger. Fire (report)- Enables issuing an updated attendance list. Folder- Eleven in number, represent the main software utilities (modules). A click on a folder displays each utility screen. (Displayed either from the Setup icon/main menu). Local- Local communication (physically connected), such as RS232 and RS485 Map- Enables a graphic display of the terminal and reader layout. Padding- A completion of empty text spaces in a field using a particular digit. PEP File- Project directories for Com-II-PRO controller unit. PIN- A personal code as a supplementary security measure. Reader- A reading unit. Security Group- A group assigned particular security parameters Terminal- A controller unit employed as a medium between the PC and readers. Time Zone- Defines a time-frame in which access is permitted. Time Zones are defined day types for a period of one year. Verify- Confirming enrolment of the fingerprint. Identify- Comparing an enrolled fingerprint, with a fingerprint stored in the terminal’s memory.

75

Troubleshooting


Chapter 17 - Troubleshooting Under Falcon’s Help (menu) | About | Info, you can find data which will be useful for technical support purposes: • Database path • Local share mode Problem

Solution to solve the problem

While sending a configuration to a You must go to Terminal list | Additions tab and check if the Max. card Master terminal a BCD (Bad Data For- value exceeds your Master capacity: mat) error message is received from the Phantom.

Permitted Master-128 Master-512 (P) Master-512 (T- Special) After installation can’t open Falcon or BDE administrator Can’t print or Preview any report Transactions are collected but not shown in the online screen and in the reports

“Index is out of date”

“Directory is controlled by another .NET file”

“Key violation” while trying to save a new person or collect data.

“Directory is busy.”

2,976 14,000 2,700

Your display is set for 16 colors, in the control panel change the display settings to a minimum of 256 colors. Define a Windows default printer Make sure the reader transaction type is not set to NONE. For Access readers: Setup| Terminal list| Master+Access| Access list| Access setup. For SY-400 readers: Setup| Terminal list| SY-400| Reader list| SY-400 Reader setup. A table has become corrupted. Exit Falcon and run Reindex.exe from the Falcon directory, while making sure no-one else is using Falcon or the database. To prevent this error: 1. Set LOCAL SHARE to TRUE on all work stations. 2. Make sure all workstations point to the same shared directory for the NET DIR setting, and the Falcon alias is exactly the same. The application terminated abnormally and left *.LCK and *.NET files floating around. Close all BDE applications and search for and delete the following files at the file server and all workstations: PDOXUSRS.NET, PDOXUSRS.LCK, PARADOX.LCK Or, multiple workstations accessing the same table are referencing the NET DIR differently. Make sure all workstations point to the same shared directory for the NET DIR setting, and the Falcon alias is exactly the same. Personnel (or Transactions) table is corrupted, exit Falcon (make sure noone else is using Falcon or the database) and from the Falcon directory run the ReIndex.exe with the /repair switch: c:\Falcon\ReIndex.exe /repair. You should see a red message “Repair option is ON” on the ReIndex program screen, press the Start button. (Please backup your database directory first!). It is possible that another BDE application is using Falcon’s private dir. (default to Windows TEMP directory). Therefore it is possible to change Falcon’s private dir location by inserting a new parameter into Falcon.ini file: [General] PrivateDir=x:\LocalPathName

76

Appendix A – CCTV Integration (PRO)


Appendix A – CCTV Integration (PRO) The Falcon software supports CCTV camera operation for remote viewing of your facility’s doorways. The following CCTV systems are supported: • Regard i and Regard Remote CS COM interface • NegeVision VideoRemote • Pelco matrix • Vicon V1500 matrix

Regard: Regard i and Regard Remote CS COM interface The Regard remote viewing servers offer remote monitoring of video cameras and other devices. Regard i was designed to serve the needs of the security industry for remote monitoring of locations with up to 8 cameras. Camera viewing is implemented via network, thus no direct connection with the camera server is required. Step 1. Under Falcon.ini fill-in: [Extensions] EnableRegard=1 Step 2. In the Terminal List folder, double click the relevant terminal and fill-in the following: Camera Site= the site as defined in Regard CS (Case sensitive). Camera Name= the camera as defined in each Regard-i box (Case sensitive).

NegeVision: VideoRemote The Video Server enables management of 4 cameras enabling remote monitoring of locations. This server enables integration between Falcon and a CCTV system. Camera viewing is implemented via network, thus no direct connection with the camera server is required. Step 1. Under Falcon.ini fill-in: [Extensions] EnableRegard=2 Step 2. In the Terminal List folder, double click the relevant terminal and fill-in the following: Camera Site= Name or IP of the Video Remote server Camera Name= the camera number in the server

Pelco: G-Protocol matrix Falcon supports camera multiplexer viewing. Multiplexers make it possible to view video streams from multiple monitoring cameras to a single viewing system. Requires a local connection from your PC to the matrix. Falcon supports the Pelco CCTV matrix family that works in RS485 and the ‘G’-protocols. It is possible to switch the active camera on the main monitor. One monitor is connected to the matrix and should be placed adjacent to the Falcon screen. Falcon controls this monitor. Step 1. Under Falcon.ini fill-in: [Extensions] EnableRegard=3 MatrixPort=n MaxricBaud=9600 “n” is the designated COM port number: 1=COM1, 2=COM2 etc. Step 2. In the Terminal List folder, double click the relevant terminal and fill-in the following: Camera Site= Matrix unit ID (usually 1 if there is one matrix)

77

Appendix A – CCTV Integration (PRO)


Camera Name= the camera number in the matrix

Vicon: V1500 Support for Vicon V1500 that works in RS-232 protocol. This device has a matrix switcher that enables connecting several cameras to it and selecting a camera to view via a corresponding monitor. A monitor should be placed adjacent to the Falcon screen to enable viewing online data and viewing the site simultaneously. Via Falcon you can determine which monitor will correspond to which camera. Step 1. Under Falcon.ini fill-in: [Extensions] EnableRegard=4 MatrixPort=n MaxricBaud=9600 “n” is the designated COM port number: 1=COM1, 2=COM2 etc. Step 2. In the Terminal List folder, double click the relevant terminal and fill-in the following: Camera Site= Monitor number to show the selected camera Camera Name= Camera number

78

Appendix B - Database


Appendix B - Database Files Access Auto4De Auto4Ma AutoDet AutoMast CLayout Com2Def Company CostCent Dates DaysType Dept Detector EvenTran Events EvntHndl Formats GenParam LuAuto LuAuto4 LuCosTyp LuEvent LuMoveTp LuPopTyp LuRdrTyp LuRunRel Maps Messages MesSys Objmap OldEvent PCardSnd PerCards PermCard Persons Reports

Access readers list SY-400 Auto-Modes, detail SY-400 Auto-Modes, master Master Auto-Modes, detail Master Auto-Modes, master Card layout design Com-II-PRO format definition Company list Calculation group list User defined calendar Calendar day types Department list Alarm detectors list Event transactions not yet closed Event definition List of predefined event handling response Transactions formats (from Phantom.FMT) General parameters List of Auto-Modes types for Master terminals List of Auto-Modes types for SY-400 terminals Calculation category types List of Events types List of Transaction types (None, In, Out, Door) List of Population types (Regular, Visitor, Guard) List of SY-400 Readers types (Magnetic, Barcode, etc.) List of SY-400 Relay Operation modes (Pulse, Set, Reset) Maps definition All software messages System messages Map items definition Closed (already taken care of) event transactions Personnel accumulated card updates to be sent to the terminals Visitor cards assignment Personnel list Visitor list User defined reports (list of *.REP files)

79


Signal SY400Rdr TerGrDet TerGrMas Terminls TimeZoDe TimeZoMa Transact TzSY4De TzSY4Ma Users Week


Event notification signalling between clients SY-400 readers list Security groups, detail Security groups, master Terminal list Master Time-Zones, detail Master Time-Zones, master All Transaction SY-400 Time-Zones, detail SY-400 Time-Zones, master Operator list Default calendar

Extensions Each table consist of one or more of the following files. When copying a table make sure you copy ALL files with the same base name. If the index files are missing or corrupted, use the Reindex.EXE program to recreate them. *.DB *.MB *.VAL *.PX *.X?? *.Y??

Database file, contain all the data Memo file, contain large notes fields Validity checks and default values Primary index Secondary indices Secondary indices

Other Files *.REP - User defined reports (SQL statements) The following files are part of the Paradox share and locking scheme and would be created automatically by the database engine if it does not already exist. If those files get out of sync, delete them and restart Falcon. PDOXUSRS.NET - Paradox network control file PDOXUSRS.LCK - Paradox lock file PARADOX.LCK - Paradox lock file

Foreign Languages Falcon’s initially installed version is English supported. (See chapter 8, Message Translation): If the support of another language is required it is recommended to copy it from an already translated source. Use the FaLang.exe utility to translate all the LU* tables (See Appendix D- Utilities). The following database files can be edited and later on copied to other installations. Their default location is C:\Falcon\DB.

80


DAYSTYPE.DB LUAUTO.DB LUAUTO4.DB LUCOSTYP.DB LUEVENT.DB LUMOVETP.DB LUPOPTYP.DB LURDRTYP.DB LURUNREL.DB MESSAGES.DB MESSYS.DB


DAYSTYPE.PX LUAUTO.PX LUAUTO4.PX LUCOSTYP.PX LUEVENT.PX LUMOVETP.PX LUPOPTYP.PX LURDRTYP.PX LURUNREL.PX MESSAGES.PX MESSYS.PX

Note: 1. When copying the database (*.db suffix) files the equivalent index (same name *.px suffix) file must be copied as well. 2.

Perform copying only while the Falcon software is shut down and no other programs use these database files.

81

Appendix C - Upgrade


Appendix C - Upgrade For your attention: It is recommended to back-up your database before updating your software. Step 1. Backup the entire Falcon directory. Make sure you backup both local and network directories. Make note of Falcon’s DB path in the BDE administrator. Step 2. When upgrading from a regular version to PRO, delete the falcon.ini file. Step 3. Copy Falcon’s 2.23 version from the FTP directory to your computer into a temporary folder (or get the latest CD distribution). Step 4. Run the setup.exe of the new version. The procedure is similar to standard installation. When requested to, choose the path of the current version (i.e.: c:\Falcon). Step 5. Run the Falcon.exe ONCE from the Falcon directory (a “Run again” message will appear). Step 6. Go to the BDE administrator and make sure the alias points to the same path as in step 1! Step 7. Run FalcUpd.exe from the Falcon directory. Step 8. An Upgrade to Falcon 2.23 window will appear. You can either accept the default option, and proceed to step 10 or: Step 9. Choose the version you are upgrading from. You can also choose either a different alias or a different directory where your current (old version) installation DB is located. Step 10. Click Start. After upgrading an Upgrade successful message will appear. Close the Upgrade window. Step 11. Run the Falcon.exe and make sure the upgrade procedure has been completed successfully. Step 12. When upgrading from versions older then 2.19 using SY-400, you must reprogram the terminals. If you are using a special SAL for your programming, make sure it is compatible with the upgraded Falcon version.

82

Appendix D - Utilities


Appendix D - Utilities The following external utilities are included in the Falcon installation: ReIndex.exe

Builds Falcon index files. Use this program when Falcon can not load due to corrupt, damaged or missing index file. This program can also Pack the database in order to improve the internal structure of the DB and to save the space of deleted records. Enables repairing transactions and authorized tables under: c:\Falcon\ReIndex.exe /repair. Back-up your database prior to the repair procedure! FalcUpd.exe

Upgrade Falcon database from an old version. See Appendix C - Upgrade.

83

Appendix D - Utilities


Those optional utilities can be found on the Falcon CD under the Utility directory: DispDb.exe

Create a text file with a complete listing of a Paradox database structure (Require Falcon 2.14 or above to be installed on the computer). FalDel.exe Delete group of people from Falcon personnel list according to defined rules. FalLang.exe Allows the user to translate and edit utility tables used by Falcon.

84

Appendix E - Master network configuration


Appendix E - Master network configuration Using Master in network communication can be implemented as follows: When your PC and Master subnet masks are identical, setting-up Master Ethernet is done by using a Telnet program. When using a different subnet mask you may: 1. Change your PC IP address to be compatible with the Master subnet mask (for example: 192.168.0.10) then use telnet or: 2. Use ARP protocol to enable access to telnet commands and then setup the required Master IP (from CoBox version 4.5 only!). Note:

In order for the ARP command to work on Windows, the ARP table on the PC must have at least one IP address defined other than its own. If the ARP table is empty, the command will return an error message. Type ARP -A at the DOS command prompt to verify that there is at least one entry in the ARP table. If the local PC is the only entry, ping another IP address on your network to build a new entry in the ARP table; the IP address must be a host other than the PC on which you are working.

Newly dispatched Masters default IP Address is 192.168.0.2 Note:

In order to avoid IP conflict make sure no other device shares your IP Address: - Disconnect the Ethernet cable from the Master. - Ping to Master IP or new terminal’s default IP. - If the IP address is confirmed, someone is using this address and you can’t use it for the Master. - If this IP address is rejected, connect the Master and retry pinging. - In case the master IP is confirmed you may setup using Telnet:

Telnet procedures: • • •

Open Telnet from Windows’ Start menu| Run, then write: telnet terminal-IP-address 9999 The device server MAC address and version are displayed. Press Enter. Basic device parameters are displayed (see table next page).

Parameter

Value

Baudrate I/F Mode Flow Port No.

9600 4C 00 3734

Connect Mode Remote IP Remote Port Disconnmode FlushMode Pack Cntrl DisConnTime SendChar 1 SendChar 2

C0 0.0.0.0 0000 00 A0 00 00:10 00 00

Comment

In Windows XP port 5000 might be occupied by another program. Choose a different port.

85

Appendix E - Master network configuration

•


You are requested to choose the relevant setup: 0 - Server configuration - Refers to IP address 1 - Channel 1 configuration- Refers to - communication settings 5 - Expert settings - Refers to the recommended network refresh timeout 6 - Security -Do not change 7 - Factory defaults - Do not change 8 - Exit without save 9 - Save and exit Type 1 and Enter.

From master ethernet card version 4.5 • • •

Type 5 (for Expert settings) + Enter Change “TCP keepalive time in s” to 45 Type 9 for save and exit

From master ethernet card version 5.1ab • • • •

Type 5 (for Expert settings) + Enter. Change “TCP keepalive time in s” to 45 Change “ARPcheck timeout in s” to 30 Type 9 for save and exit

Using ARP Command In order to use the ARP IP setting commands you should know the Ethernet MAC address (Start from paragraph 5). If you do not know the MAC address do the follows: 1. Open the terminal cover. 2. Remove the Ethernet card and write the MAC address (indicated on a sticker), i.e: 00-20-4A-54-5A-12. 3. Connect the Ethernet card. 4. Connect the Master to your local network or to the HUB that connects to the PC you wish to use. 5. Use Windows Start menu| Run or the Command Prompt and run “arp -s (New IP) (MAC address)” 6. Run Telnet (new IP) port 1. 7. Run Telnet according to Telnet procedures. 8. Try communicating using the new address. ARP example: Terminal MAC address: 00-20-4A-54-5A-12 Requested IP: 192.168.2.128 Commands format should be: arp -s 192.168.2.128 00-20-4A-54-5A-12 telnet 192.168.2.128 1 When a “Connection failure” message appears - ignore it! telnet 192.168.2.128 9999 Edit 0 - Server configuration Change Master IP address to new IP. Run Telnet according to Telnet procedures. Exit and save.

86

Appendix F - Error Messages


Appendix F - Error Messages Origin

Parameter

“Index is out of date” System (Borland) Messages

Solution A table has become corrupted. Exit Falcon and run Reindex.exe from the Falcon directory, while making sure no-one else is using Falcon or the database. To prevent this error: 1. Set LOCAL SHARE to TRUE on all work-stations. 2. Make sure all workstations point to the same shared directory for the NET DIR setting, and the Falcon alias is exactly the same.

“Directory is controlled The application terminated abnormally and left *.LCK and *.NET by another *.NET file” files floating around. Close all BDE applications and search for and delete the following files at the file server and all workstations: PDOXUSRS.NET, PDOXUSRS.LCK, PARADOX.LCK Or, multiple workstations accessing the same table are referencing the NET DIR differently. Make sure all workstations point to the same shared directory for the NET DIR setting, and the Falcon alias is exactly the same. “Key violation” while trying to save a new person or collect data.

Falcon Messages

Personnel (or Transactions) table is corrupted, exit Falcon (make sure no-one else is using Falcon or the database) and from the Falcon directory run the ReIndex.exe with the /repair switch: c:\Falcon\ReIndex.exe /repair. You should see a red message “Repair option is ON” on the ReIndex program screen, press the Start button. (Please backup your database directory first!).

Operator or password are invalid. Fill-in the correct operator details Confirmation failed Confirmation password and password. does not match new password! Invalid password Access denied.

It is impossible to operate the program because an invalid password was filled-in several times.

Card number validation Each employee must be assigned a card number. - card length equals 0. Card number validation A card number must not contain letters, marks, symbols or spaces. It - Card number must must be comprised of digits only. contain digits only! Duplicate card number - There is a unique card number for each employee. Fill-in another Unable to post. number (or check if the number you just fill-in assigned to another employee). Error from Phantom

An error has occurred during the operation of Phantom. For further information refer to Phantom’s message list.

Starting Online Scan No active terminal was selected for this operation.

The check box Participate in online scan is not marked in either of the terminals in the terminal list. Please mark he relevant terminals as per you requirements.

Wrong port Open Port Error

In the Terminal setup screen under Communication define an existing/ available port.

87

Appendix F - Error Messages Origin


Parameter

Solution

Programming- Error creating tables

Check the project directory path in the General Parameter screen under Files and Directories. Then, make sure such a directory does exist and that the user has access to that directory. Moreover, check for all SY-400 terminals under the Additions tab, that the Project directory path is correct.

No terminals were selected for this operation!

No active terminals were defined in the system or the no terminal was marked in the Communication screen.

Please send Permitted from Communication screen.

Personnel| Send Last is supported by Master terminals only. For SY-400 you must wait for the next update.

Invalid Date/Time value

Under Communication fill-in valid date before sending data to the terminal.

Report does not exist!

A report that was previously stored by the report generator can not be issued. It is possible that the report configuration file was miscalculate. Define report parameters again using the report generator.

Undefined terminal

As the security group table is corrupted, the wrong terminal type was registered, delete this row and add a new row if required.

Upto 255 terminals can It is impossible to add a new terminal to the terminal list. Please refer be defined! to a Synel representative for system expansion as per your requirements. File not found!

File or program do not exist.

Error!

A general error message that is usually followed by a general description of the problem (English text).

Error saving picture to disk!

Make sure the user has Write permission to the Pictures folder and that an operation system induced read-only Pictures folder does not already exist!

File could not be opened/created!

Check export file location: if the alias is to an existing directory in which the user is Write permitted. Make sure the file is not occupied by another process.

Table is empty!

Nothing more to delete, the table is empty!

Record not found!

Choose different sorting (name, ID etc) or maybe the employee does not exist.

Error opening table!

Error when issuing Message report, retry issuing the report. If the problem recurs refer to Synel.

File is used by another user! Can not re-index now.

Probably the file is occupied by another program/user. Exit all programs that refer to Falcon’s data base and then try reindexing.

Error creating report!

A text in English usually follows, indicating the reason. Report the specific text to Synel’s technical support team.

Close the Preview first! There is an open/minimized window of the Preview screen. Please close it or try to re-enter the program. Error exporting file!

The file can not be exported. Write a valid file and directory names for the export file.

88

Appendix G - SY-Server


Appendix G - SY-Server To perform online checks, Falcon uses SY-Server as a communication program. SY-Server uses a compatible DLL that verifies incoming data and writes to Falcon’s database. To install SY-Server you must refer to the relevant documentation or to our technical support department. After you have installed SY-Server, you must: • • •

Set SY-Server definitions Set Falcon definitions Set DLL definitions

SY-Server Definitions Change the settings as per the following screens: 1.

2.

The marked parameter which is the only relevant parameter in the following screen, must be checked.

89

Appendix G - SY-Server 3.


Under Setup | General, define your Query/Data Header settings as follows:

Falcon Definitions 1.

2. 3.

In the SY-400 terminal parameters screen: • Under Additions Fill-in a value larger than 0 under Automatic Data Send Freq. (recommended value between 1-10 seconds). • Under FPU you must determine the FPU mode, to enable online fingerprints validation (for prints that are not stored in the terminals memory). In the SY-400 reader parameters screen | Validation: Mark the Host check box. If the reader participates in Global APB, mark this check box as well. In the General Parameters | Communication mark the Write Last Transaction into Personnel File (used for Global APB checks).

DLL Definitions Under Utility\SySrv400.dll in your Falcon CD you will find two variations of the same DLL: 1. 2.

FlconDLL.dll- Standard DLL operation FlconDBG.dll- Same as the standard DLL, in addition it logs every activity to debug.dat file.

To adjust your standard DLL you can edit the following sections in the FlconDLL.ini file: • • • • •

Card number validation (including time zone per security group) Global APB Calculation Group SyGina (PC Security Lock) Stolen Cards

90

Manual Falcon version 223 English

Recommend Documents