PMT Security

Advanced Access Control

Uncategorized

Creating an Input on a Wiegand Reader Module to Generate a Lockdown/Emergency Mode For a Single APC Controller In OMNIA

Creating an Input on a Wiegand Reader Module to Generate a Lockdown/Emergency Mode For a Single APC Controller In OMNIA

How to create an input that will put the single APC Controller into Lockdown or Emergency Mode in OMNIA

Emergency
Emergency inputs are associated with fire alarms (3rd Party System Activation) or emergency call points (Manual Activation).
Activating this input will raise an Emergency event that will unlock all your
emergency doors.
In the following example, we will use the DOS (Input 1) input on a Wiegand Reader Module to activate Emergency.

Input Emergency Mode Off Input Emergency Mode On Wiegand Reader Module (Input 1)

REMEMBER: DOS is always input 1 and RTE is always input 2

Lockdown 

Lockdown inputs are associated with Intruder/Active Shooter emergency call points.

Activating this input will raise a Lockdown event that will prevent the unlocking of your emergency doors.

In the following example, we will use the RTE (Input 2) input on a Wiegand Reader Module to activate Lockdown,

Input Lockdown Mode Off Input Lockdown Mode On Wiegand Reader Module (Input 2)

REMEMBER:  DOS is always input 1 and RTE is always input 2.

Location of Input 1 (DOS) and Input 2 (RTE) on Wiegand Reader Module for OMNIA

Note
This method will only affect the doors connected to the same system controller
as this Wiegand Reader Module. To activate Emergency mode across multiple controllers, see Configuring Emergency Input Across Multiple Controllers

Configuring an Emergency Input

These steps apply to any reader in any profile

  1. Open the Reader Profile ( Ensure this contains the correct reader being used for the input ) or Create a New Reader Profile ( Ensure you select the correct Reader being used for the input ) For This Scenario , a new Reader Profile was created. Reader Profile named Lockdown/Emergency. For Simplicity we have used the same Wiegand Reader Modules inputs for both Lockdown (Input 2)  and Emergency (Input 1). The Wiegand Reader Modules Fixed Address is 005DC20.
  2. Select Inputs then select Add Input
  3. Name the input.
  4. Select the type of input, for this case Emergency or Lockdown
  5. Select the Contact State and Input Number
  6. Save

1.  Open the Reader Profile

Located under Set-Up - Open Reader Profiles > Lockdown / Emergency, Select Readers Tab

Select the Reader the Inputs are associated with.

Select the Reader the Inputs are associated. Eg. Quick Door 3 (IN)

2. Select Inputs then select Add Inputs.

Select Inputs Tab, then Select "ADD INPUT"

3. Name the input.

4. Select the type of input, Lockdown or Emergency

Select the "type" of input, Lockdown or Emergency.

5. Select the Contact State and Input Number

REMEMBER:  DOS is always input 1 and RTE is always input 2.

Lockdown

Lockdown Select the Contact State and Input Number REMEMBER:  DOS is always input 1 and RTE is always input 2.

Emergency

Emergency Select the Contact State and Input Number REMEMBER:  DOS is always input 1 and RTE is always input 2.

Emergency and Lockdown Behavior
After creating an emergency or lockdown input, you need to decide how all your readers
will behave during Emergency Mode and Lockdown Mode.

Emergency Mode

By default, your readers will flash green but no relays will drive. The state of the relays will need to be changed.

Lockdown Mode

By default,  your readers will flash red and no relays will drive


To configure the Modes: go to, Setup>Hardware>Reader Profiles> select profile >Behavior


Steps:
1. Select the Reader Profile for the readers you wish to unlock/lockdown
2. Select the Behavior then Edit Behavior

3. Search for Emergency/Lockdown
4. Select Output States
5. Select Relay Contact State then for Emergency Mode select Drive relay in this mode, for Lockdown leave section at Do Not Drive Relay

Under Setup Tab, Select Reader Profiles > Default Reader Select Behaviour Tab Click "EDIT BEHAVIOR"
Select E (Emergency) or L (Lockdown)

Emergency

Emergency Relay Contact State Drive relay in this mode

Lockdown

Lockdown Relay Contact State Do NOT drive relay in this mode

Now all the readers in the selected Reader Profile will drive their relays during
Emergency Mode and will not drive relays in Lockdown Mode. Repeat these steps for any other required Reader Profiles.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

How to set OMNIA Access Groups, Areas, and Device Time Patterns

OMNIA Access Groups, Areas, and Device Time Patterns

OMNIA Access groups is the feature that determines where and when people have access.

OMNIA Access groups are made up of three main components;

  1. Areas (Where people have access)
  2. Time Patterns (When people have access)
  3. Holidays (Control access on public holidays)
OMNIA - Enrolment - Access Groups

Creating Access Groups in OMNIA

  • Set up different Areas according to your requirements
  • Set up Access Time Patterns according to your requirements
  • Enter any relevant public holidays
  • Create Access Groups by linking Areas with Access Time Patterns

Area + Time Pattern = Access Group

Areas in OMNIA

Areas determine the doors people have access to. Create different areas for each department in your facility and select the doors that will be available to that Area

How to create a new Area

  • Navigate to Enrollment > Access > Areas
  • Click on the blue + to create a new Area
  • Give the area a descriptive name
  • Save by clicking Green Check
In OMNIA navigated to Enrollment, select Access, then select Areas, click the blue '+' symbol to create a new Area.
Describe the Area and Save
  • Expand the Door Selection Tree
  • Select the doors that will be accessed
  • Save
Expand the Door Selection Tree, Select the doors that will be accessed in this area and save again.

Similar matches

Avoid creating duplicate areas by looking at Similar Matches. Duplicate areas in the database would create an untidy system.

If you have a 100% match with an existing area, consider using that Area instead of creating a new one.

Access Time Patterns

Access Time Patterns determine the times when people have access. Create different time patterns for each department in your facility.

How to create a new Access Time Pattern

Navigate to Enrollment > Access Time Patterns

  • Click on the blue + to create a new Access Time Pattern
  • Give the pattern a descriptive name
  • Choose the start time
  • Choose the end time
  • Select the days of the week
  • Save
In OMNIA to create a new Access Time Pattern, navigate to Enrollment, Select Access Time Patterns, select the blue '+' to create a new Access Time Pattern. Describe the time pattern, select your start and end times, select the days of the week and then save using the green check mark button.

Holidays can be used to control access on public holidays.

Holidays are not set up automatically. Enter all relevant public holidays during the beginning of each year.

How to set up holidays in OMNIA

  • Navigate to Setup > System > Holidays
How to set-up holidays in OMNIA, navigate Setup > Systems > Holidays Select '+' to create a new entry.
  • Click on + to create a new entry
  • Give the holiday a descriptive name
  • Choose the start date
  • Choose the end date
  • Enter a description (Optional)
  • Save
Describe the holiday, select start and end date, and save using green check mark button.

To control access on holidays, use the Public Holiday tick found in Access Time Patterns

To control access on holidays, use the Public Holiday tick found in Access Time Patterns.

Holiday Report

For a quick report on which holidays have been set up, run a holiday report under Reports

Enrollment

Enrolment is the process of creating ‘Tagholders’ and assigning access credentials like; Tags or fingerprints.

Tagholders need to be assigned at least one Access Group in order to access specific doors.

Tagholders need to be assigned at least one Access Group in order to access specific doors. To create a new Tagholder, navigate to Enrolment > Tagholders
  1. Create new Tagholder (Save)
  2. Add Image (Optional, but recommended)
  3. Add Tags
  4. Assign Access Groups

Adding a new Tagholder in OMNIA

A Tagholder is any person who uses a Tag or Fingerprint to access your site. 

OMNIA licensing will determine the maximum amount of Tagholders allowed per site. 

To add a new Tagholder

  • Navigate to Enrollment > Tagholders
  • Click on New
  • Fill in the compulsory fields ( First Name, Last Name, ID, Display Name)
  • Fill in any additional information (Contact info, Department, Company)
  • Save
To add a new Tagholder select the blue '+' button.
Fill in Tagholder information, only after saving will tags, access groups and photo options become available.

Note: Only after saving will the Tags, access groups and photo options become available.

OMNIA features available after initial tagholder setup and save.

Adding Images

You will only be able to add pictures after saving a new Tagholder. Portal allows for 3 Images per person. These could include ID/Passport images

  • Click on the pencil icon
  • You can either browse to a saved picture or take new picture using a webcam
  • You can edit the image rotation and color settings by clicking on Edit Picture
Click on the pencil icon to edit tagholder image.

Adding Tags

‘Tags’ are the credentials used by Tagholders to gain access to your site. Tags can be cards, keyring-fobs or fingerprints.

Note: The Tags option will only appear after you save the Tagholder’s compulsory fields.

Adding a new Tag:

  • Select the Tagholder and go to Tags
    • Click on ADD TAGS
  • Click on ENROLLMENT WIZARD
  • Click on Enroll Card
  • Choose Enrollment Option
Adding New Tag Select the Tagholder and go to Tags Click on ADD TAGS
Click on ENROLLMENT WIZARD
Click on Enroll Card Choose Enrollment Option

Add start and end dates (Optional) Save. 

NOTE: You MUST have a start date to set an expiration date.

Add Start and End Dates

Assigning Access Groups

Access Groups determine where and when Tagholders have access, select the applicable Access Groups in their Tagholder configuration.

Select the Access groups applicable to the Tagholder.

Select OMNIA Access groups applicable to the Tagholder.

Temporary access

To grant temporary access to a specific area, use the area expiry feature. This will disable the selected Access Group according to the end date

To grant temporary access to a specific area, use the area expiry feature. This will disable the selected Access Group according to the end date.
Fill in Expiry Date/Times

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

AmanoNet Minimum PC Requirements and Specifications

AmanoNet Minimum PC Requirements and Specifications

Consider a number of factors when determining the correct PC specifications for different scenarios. The Database Server usually has the highest specification requirements.

Consider the following factors when specifying the Database Server:

  1. Number of doors (Terminals)
  2. Number of Tagholders supported by the System
  3. Number of client (Module) connections to the Database

Database Server

NOTE:  The number of client connections to the Database Server will affect the performance of the Database Server. Adjust the specification allowing for all client connections to perform Database tasks efficiently.

NOTE:   The volume of transactions per Site affects the performance of the Database Server. Adjust the specification allowing for rapid Database growth and Reports that work with large result sets.

NOTE:   This specification is for a dedicated Database Server only, without additional Software (third-party or AmanoNet Modules).

AMANONet Module PC’S

IMPORTANT:   Ensure that you install all AMANONet Modules on dedicated PC’s.

Standard Software Modules
(Engine, Access (including Card Designer), QuickTag, Visitor, Transaction Viewer, Alarms Client)
Optional Client Software Modules (Graphics Designer, Graphics Runtime)
Optional Server Software Modules (Impro Touch, Impro Vision)

NOTE:  The number of third-party devices that are used by each optional Server affects the performance of the System. Adjust the specification to allow the optional Servers to run at an optimal level.

NOTE:  The number of client connections to each optional Server affects the performance of the System.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

AmanoNet Back up using IB Console

AmanoNet Back up using IBConsole

IBConsole is a relational database management utility allowing connection to and administration of multiple Firebird Servers and Databases.

The entire functionality of IBConsole is beyond the scope of this document; however administrators of Impro Access Control Databases may find the following roles within IBConsole useful:

  • Database maintenance in the form of database sweeps and checking for errors.
  • Backup and Restores of the database.
  • Review of the database structure, allows addition of extra tables for third-party integration.

The first step in connecting to an AmanoNet Database is registering the Database Server. The following examples refer to the default Database AmanoNet.fdb used by the ImproNet Software suite. The default locations for the Databases and the IBConsole Utility varies dependant on the Access Control System used.

Start the IBConsole Software

From the PC go to C:/AmanoNet/Tools/IBConsole/IBConsole.exe

Register the Server

You need only perform these steps once. After registration, the settings remain and you are only required to login to the Server.

  1. From the Server drop-down menu, select the Register choice.
  2. In the Register Server and Connect dialog, click the Remote Server radio button.
  3. In the Server Name textbox, assign the Server a name. In this example, we used LOCALHOST.
    • NOTE: Rather than assigning the Server a name in the Server Name textbox, you may use the PC’s IP Address
  4. In the Network Protocol textbox, select TCP/IP from the drop-down list.
  5. In the Alias Name textbox, assign a meaningful name.
  6. Leave the remaining fields unchanged.
  7. Click the OK button.

NOTE: Rather than assigning the Server a name in the Server Name textbox, you may use the PC’s IP Address

Login to the InterBase Server

  1. From the Hierarchical Tree, select your InterBase Server (based on the example in Figure above select Local Server).
  2. From the Server drop-down menu, select the Login choice.
  3. In the Server Login dialog, enter the Username and Password.
  4. The default username is SYSDBA. The default password is masterkey.
  5. Click the Login button.

Register the Database

  1. From the Database drop-down menu, select the Register choice.
  2. In the Register Database and Connect dialog, In the Database textbox, enter the full file path to your Database (see Figure above).
  3. Click your mouse pointer in the File textbox, the Database’s file name automatically appears.
  4. Leave the remaining fields unchanged.
  5. Click the OK button.
    • The default Database path for the AmanoNet Software suite is: C:\AmanoNet\databse\AmanoNet.fdb.
  6. In the Hierarchical Tree, double-click on the AmanoNet.fdb file, starting the Database.

Database Backups

Administrators of Impro Access Control Systems have various options for making a backup of their Access Control Database. The simplest option employed, is copying the Database.

Copying the Database simply copies the Database irrespective of whether there is corruption of the Database or not.

Before making a copy of the Database ensure that you shut down the Access Control Software.

The preferred method of making a backup is to use the built in (automatic) backup features in the AmanoNet Software.

Scheduling the backup of an AmanoNet Database

  1. In the PC go to C:/AmanoNet/bin/AmanoNet/AmanoNet Engine.
  2. From the Configuration drop-down menu, select Backup.

In the Backup dialog, alongside the Backup Path textbox, click on the button.

NOTE: The backup path automatically defaults to the local workstation. For storage purposes, ensure that you change this backup path to a remote server. Engine does not allow the use of spaces within the backup path.

  1. In the Number of Backups to keep in Backup Folder textbox, enter a suitable number.
  2. From the Schedule group specify the days and times you wish to perform the backups.
  3. Click on the button.
  4. Ensure that you schedule the backups when Engine is open and running.
  5. Shutdown and restart the Engine module for the changes to take effect.

During the backup procedure, the backup utility takes a snapshot of the working database, the snapshots compacted and a new file created. The resulting backup file has an fbk file extension.

NOTE: A backup does not guarantee that your ImproNet Database is free from corruption. Ensure that you carry out regular database maintenance, thus ensuring that your ImproNet Database is not corrupt.

For unscheduled backups use either of the following choices:

  • Backup the ImproNet Database using IBConsole.
  • Backup the ImproNet Database using a Batch File.

Backup the AmanoNet Database using IBConsole

  1. In the PC, go to C:/AmanoNet/tools/IBConsole.
  2. From the Database drop-down menu, select Maintenance > Backup / Restore > Backup.
  1. In the Database group, from the Alias drop-down list, select the Database for backup.
  2. In the Backup File(s) group, in the Alias textbox, provide a name for the backed up Database. Ensure that your backed up file has an FBK file extension.
  3. In the Backup File(s) group, in the Filename(s) textbox, provide the directory path and file name for the backup Database. We suggest C:\AmanoNet\Database\AmanoNet.fbk.
  4. Leave the remaining values as they are.
  5. Click on the OK button.
  6. In the Information dialog, click on the OK button.
  7. Close the Database Backup dialog.

Database Restore

Perform a Database restoration for the following reasons:

  • Your original AmanoNet Database becomes corrupt.
  • Your PCs hard drive is damaged for any reason.
  • To ensure that Database backups are not corrupt, a successful restoration suggests a sound Database.

Restoring the Net Database Using IBConsole

Disconnect from the Database

  1. In the PC, go to C:/AmanoNet/tools/IBConsole. 
  2. From the Hierarchical Tree, click on the Amanonet.fdb file.
  3. From the Database drop-down menu, select Maintenance>Shutdown.

Restore the Backup

In IBConsole, from the Database drop-down menu, select Maintenance > Backup / Restore > Restore.

  1. In the Backup File(s) group, in the Alias textbox, select the name of the backed up Database. If IBConsole does not auto complete the remaining fields continue as follows, otherwise continue with point 4:
    •  In the Backup File(s) group, in the Filename(s) textbox, provide the directory path and file name for the backup database. We suggest C:\ImproNet\Database\ImproNet.fbk.
    • In the Database group, from the Server drop-down list, select the server in which the Database will remain.
    • In the Database group, from the Alias drop-down list, select the Database to restore to.
    • In the Database group, in the Filename(s) textbox, provide the directory path and file name for the restored Database. We suggest C:\ImproNet\Database\ImproNet.fdb.
  2. From the Options group, select the Overwrite record.
  3. From the Overwrite drop-down list, select True.
  4. Click on the OK button.
  5. Close the Database Restore dialog when you see the comment ―Service Ended‖.

Reconnect to the Database

  1. In IBConsole, from the Hierarchical Tree, click on the Impronet.fdb file.
  2. From the Database drop-down menu, select Maintenance > Restart.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Archive Transactions in AmanoNet

Archive Transactions in AmanoNet

This Utility lets you archive transactions (Normal, Status and Alarms), placing the transactions in a separate archived Database. We recommend that you run the Archive Utility on a regular basis. Running Utility regularly keeps your Database below the maximum recommended database size of 2 GB.

This action has two major benefits:

  1. Manages the size of the Database, freeing up space on the PC.
  2. Keeps a cleaner, uncluttered Database.

Opening and Using the Archive Utility

  1. go to C:\AmanoNet\Bin\Archive.exe
  2. Enter your Username and Password.
  3. NOTE:  The Default Username is sysdba. The default password is masterkey

Select the Archive Date

This is the end date for the archive. Your newly archived database will therefore contain all transactions for this date and earlier.

  • In the Database Archive Utility dialog, in the Archive Date group, click on the Change button.
  • In the calendar dialog, click on the Month drop-down list and select the desired month from the list.
  • Click on the Year drop-down list and select the year from the list.
  • From the grid, select the day number.

Confirm the Archiving Options

  1. In the Database Archive Utility dialog, click on the Options button.
  2. In the Archiving Options dialog, click either the Archive or Delete radio button for each of the named transaction types.

NOTE: If you select the delete option, confirm the deletion in the Delete Transactions dialog, by clicking on the OK button. After confirmation, the Archiving Options dialog closes automatically.

Archive the Transactions

  • In the Database Archive Utility dialog, click on the Archive button.
  • In the Archiving Options dialog, confirm the archiving details by clicking on the OK button.

Click on the OK button.

In the Archive Complete dialog, click on the OK button.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems