• Skip to primary navigation
  • Skip to main content
PMT Security Logo

PMT Security

Advanced Access Control

  • Home
  • About Us
    • Our Partners
    • Our Integrators
  • Solutions
    • Residential
    • Government Facilities
    • Education
    • Retirement
    • Manufacturing
    • Retail Businesses
    • Campgrounds & Outdoor Resorts
  • Products
    • Access Control
      • Control Features
      • Reporting & Monitoring
      • Control Module
      • Digital IO Module
      • Reader Module
      • Readers
    • Video Management
      • Analytics
      • Security Cameras
    • Visitor Management
  • Support
    • Knowledgebase
    • Download Center
    • License Request
    • RMA Request Form
  • Blog
  • Contact Us

OMNIA

Unlock On First Tag In OMNIA

Unlock On First Tag In OMNIA

Steps to set up unlock on first tag presentation in OMNIA

Purpose:

Unlock on First Tag feature provides the facility of unlocking selected door(s) when the first valid Tag is presented during a specified time period. The door remains unlocked for that time period, but is locked outside that time period, opening only on presentation of a valid Tag.

In the following example procedure, activate the Unlock on First Tag feature only on weekdays from 7 am to 5 pm. This means that, in OMNIA, you must create the following Device Time Patterns, Create a New Reader Profile, Create New Relay Actions using the New Device Time Patterns, then apply the New Actions to the Allowed Normal In Events for the desired Readers.

Step 1:

Create Device Time Patterns

  • A Device Time Pattern from 7 am until 5 pm on weekdays (Monday to Friday). This is the period for which the Unlock on First Tag feature must be enabled.
  • A Device Time Pattern from Sunday until Friday, 5 pm until 12 am. This is the remaining time on each of the above days during which the Unlock on First Tag feature must be disabled.
  • A Device Time Pattern from Sunday until Friday, 12 am until 7 am. The Sunday period covers the time from midnight to 7 am on Monday.
  • A Device Time Pattern called Deactivate Relay at 5pm. Set the start time to 5 pm and select Monday to Friday. This will End the Unlock on First Tag
  • A Device Time Pattern for Saturday, Sunday and public holidays for the full 24 hours. These are the days on which the Unlock on First Tag feature must be disabled.

Create Device Time Pattern

1.  Go to Setup

2.  Device Time Patterns.

3.  Click the plus to create a new Time pattern

4.  Name the Time Pattern something familiar

5.  Enter the Start Time and End Time: This will be the time frame that the unlock on first tag will be valid for.

6.  Select the Days of the Week for this time pattern.

7. Select the Save Button

Repeat the processes mentioned in steps 2 to 7 for the remaining Device Time Patterns.

Step 2:

Create a Reader Profile for the readers/doors needing the Unlock on First Tag Scenario

Create Reader Profile

1.  In the OMNIA URL, Go to  Setup

2.  Reader Profiles

3.  Click the plus to create a new Reader Profile

4.  Name the Reader Profile something familiar

5.  Select Copy of Default Reader Template, System Site

6.  In the Reader Profile, Select Readers

7.  Select the Reader the Unlock On First Tag will be applied to. Select all doors that will have the First Tag Unlock.

In this example we will be using the Front Door

Step 3:

Create New Actions in the Unlock On First Tag Reader Profile

Create New Action 7am-5pm Mon-Fri

Go to Setup/Reader Profiles/Unlock on First Tag

NOTE: This Action enables the relay for an indefinite period.

1.  Select Actions

2.  Select Add Action  

3.  Name the Action

4.  Along side the Type Section, Select the Browse Arrow

5.  From the list displayed select Relay – Action 1

6.  Select Activate Relay

7.  Select Relay 1

8.  Set the Duration to 65535 (Indefinite)

9.  Select the Browse Arrow to open the Device Time Pattern Selection

10.  From the list of Displayed Time Patterns, select the 7am-5pm Mon-Fri Device Time Pattern.

11.  Select Save

Create New Action Mid-7am Mon-Fri

NOTE: This action prevents First Tag Unlock before the Unlock on First Tag Time Period

1.  Select Actions

2.  Select Add Action  

3.  Name the Action

4.  Along side the Type Section, Select the Browse Arrow

5.  From the list displayed select Relay – Action 1

6.  Select Activate Relay

7.  Select Relay 1

8.  Keep the duration at 40 

9.  Select the Browse Arrow to open the Device Time Pattern Selection

10.  From the list of Displayed Time Patterns, select the Mid-7am Mon-Fri Device Time Pattern.

11.  Select Save

Create New Action 5pm-Mid Mon-Fri

NOTE: This action prevents First Tag Unlock after the Unlock on First Tag Time Period

1.  Select Actions

2.  Select Add Action  

3.  Name the Action

4.  Along side the Type Section, Select the Browse Arrow

5.  From the list displayed select Relay – Action 1

6.  Select Activate Relay

7.  Select Relay 1

8.  Keep the duration at 40 

9.  Select the Browse Arrow to open the Device Time Pattern Selection

10.  From the list of Displayed Time Patterns, select the 5pm-Mid Mon-Fri Device Time Pattern.

11.  Select Save

Create New Action 24hrs Sat, Sun, Holiday

NOTE: This action prevents Unlock on First Tag  for Saturday, Sundays and Holidays.

1.  Select Actions

2.  Select Add Action  

3.  Name the Action

4.  Along side the Type Section, Select the Browse Arrow

5.  From the list displayed select Relay – Action 1

6.  Select Activate Relay

7.  Select Relay 1

8.  Keep the duration at 40 

9.  Select the Browse Arrow to open the Device Time Pattern Selection

10.  From the list of Displayed Time Patterns, select the 24hrs Sat, Sun, Holidays Device Time Pattern.

11.  Select Save

Create New Action Deactivate Relay at 5 pm

Note: This action locks the door at 5pm

1.  Select Actions

2.  Select Add Action  

3.  Name the Action

4.  Along side the Type Section, Select the Browse Arrow

5.  From the list displayed select Relay – Action 1

6.  Select Deactivate Relay

7.  Select Relay 1

8.  Keep the duration at 40

9.  Select the Browse Arrow to open the Device Time Pattern Selection

10.  From the list of Displayed Time Patterns, select the Deactivate Relay at 5pm Device Time Pattern.

11.  Select Save

Step 4

Assign the Newly Created Actions to the Allowed Normal In Events for the Reader\Door.

Go To Setup\Readers\Front Door\Actions

Select Actions

Select Event Actions

Select the Browse Arrow the Event and scroll or search for Allowed Normal In

Select the Filter Option for Actions Assigned and select the show assigned actions

The Default Actions are displayed, The Newly Created Actions need to be added to the actions that will occur when an Allowed Normal In Event happens at this reader/door. The Default relay action needs to removed.

Uncheck the Show Assignments Only box and search for and add the newly created actions.

Add the Actions to the Event by putting a check in the box the left of the action.

Knowledge Base Article Writing Area

Text

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

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

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

Deleting Tag Holders in OMNIA

Deleting Tag Holders in OMNIA

How to Delete Tagholders in OMNIA

In the OMNIA URL, Go to Enrollment, then select Tagholders.

Open OMNIA URL, Select  "Enrollment" from Navigation, then Select "Tagholder" located under the heading "Types"

Scroll down to the Tagholder to delete, hover over the Tagholder and select the Delete Button.

Scroll down to locate Tagholder to delete, hover over the Tagholder and select the Delete trashcan icon.

Select Confirm to complete the deletion

Select "Confirm" to complete the deletion.
Tagholder no longer listed. Repeat steps to delete another tagholder.

Repeat as necessary.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

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

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

Database Migration from Nexus220/IXP220 to OMNIA

What Data is Migrated from Nexus220 during a Database Conversion?

PMT Security offers a conversion service to migrate data from an Nexus220 system to an OMNIA system. It is however a limited migration and only select data is migrated.

Database migration from Nexus220/IXP220 to OMNIA

The following data IS migrated from the IXP220 database:

  • Limited master data (first name, last name, ID number, company)
  • Tagholder images
  • Departments and department assignments
  • Tags
  • Access groups and access group assignments
  • Access time patterns and assignments
  • Biometric templates (fingerprints)

The following data IS NOT migrated from the IXP220 database:

  • Hardware (controllers, terminals, readers, including 3rd party biometric readers)
  • Doors
  • Areas
  • Transactions
  • Operators
  • Other miscellaneous settings not mentioned in the list of migrated data

If there is a need to refer to transactions from the Nexus220 system for historical purposes, it is recommended that this is done via Nexus220 reports from the old Nexus220 database.


Hardware must be installed again the new system, doors created and assigned to areas. Areas can be linked to the migrated access groups to restore correct access assignments to tagholders.


IXP220 system controllers are not compatible with OMNIA, and must be replaced with the appropriate controller for the new system.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Nexxus220

Change Default Password in Nexus220
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220
Replacing Nexus220 Controller with APC Controller and Wiegand Reader Module

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

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

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

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

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220

Omnia

Adding Widgets to the OMNIA Dashboard

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Deleting Tag Holders in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

Adding Widgets to the OMNIA Dashboard

Adding Widgets to the OMNIA Dashboard

The OMNIA dashboard is the central hub for your access control system, the dashboard allows you to easily see useful information and make commonly used tasks available in one central page.

The OMNIA dashboard is the central hub for your access control system, the dashboard allows you to easily see useful information and make commonly used tasks available in one central page. 

From the dashboard, you can view status of doors, see live access transactions, view health aspects of the system and set up shortcuts that allow you to quickly do common tasks without having to leave the dashboard. 

Here is a list of available widgets: 

  • Access Group capacity Graph – Shows a graphical representation of people with a particular access group that are inside a given zone. 
  • Commands – Shows executable commands such as remote door open. 
  • Enrollment Graph – Total enrollments for the week and highest, lowest enrollments. 
  • Find Image – Shows the images of the person with matching id number. 
  • IP Camera – View live feed from an IP camera. 
  • Last 10 Transactions – Shows the last 10 transactions for a person. 
  • Live! – Shows a live view of access in the system. 
  • Monitor Comms Queue – Shows total queue size and total offline controllers. 
  • Monitor Door – Monitor a single door or reader on site. 
  • Quick Enroll – Enroll a person or asset. 
  • Shortcut – Shortcut loads a user defined view when clicked. 

Setting up the Dashboard. 

Once logged in to OMNIA, select the menu item at the top left ‘Dashboard’. 

To add a widget, click on the blue plus sign at the top right.   

You will be presented with a menu: 

Click on the arrow to bring up a list of available widgets. 

Select the widget that you wouls like to use: 

Here I have sellected “Commands” and Set the command to act on a site level, this will allow me to reset Anti-Passback on the site. 

Note that you can customize the widget colors. 

The dashboard optimizes itself, always trying to fill empty space, so newly created widgets will fill from the top left, you can move widgets by dragging them. 

Once your widget is where you want it, click the green check at the top right.  

This is the completed widget. From here you can put the site into LOCKDOWN (If configured), EMERGENCY LOCKDOWN (If configured) or reset APB LOCKDOWN (If configured).  

Here is an example of a well populated Dashboard: 

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

General

Can I initiate RS485 comms to a terminal from an existing IP terminal?

How to Select the Right Cable for the job

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Network Configuration – Best Practices

Technical Bulletins

OMNIA Run as a Service fix for v4.x

Access Control

AmanoNet

AmanoNet Back up using IB Console

AmanoNet Minimum PC Requirements and Specifications

AmanoNet System Migration Notes

Archive Tagholders in AmanoNet

Archive Transactions in AmanoNet

AutoID IP Hardware in AmanoNet

How to move AmanoNet Access Control System from one PC to another (Firebird)

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

ImproNet/AmanoNet Database Backup: SQL

NOTICE! UPGRADE TO AMANONET 7.74 – EC2/400i NO LONGER AVAILABLE

Nexxus220

Change Default Password in Nexus220
Database Migration from Nexus220/IXP220 to OMNIA
How to fix a Java SE Binary Error in Nexus220 Software
How to get a copy of a database from Nexus220 Software
How to move Nexus220 to a different PC
IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220
Move Nexus220 Access Control System from one PC to another (Firebird)
Nexus220 Firmware Upgrade
Nexus220 Notifications Configuration/Email Configuration
Nexus220 The number of doors for this license has been exceeded
Nexus220 Web Reports Using Microsoft Edge
Reduce length of time on buzzer for readers in Nexus220

Omnia

Basic Trouble Shooting OMNIA

Batch Operations OMNIA

Change SYSDBA Password in OMNIA

Configuring Web Session Timeouts in OMINA

Create a Database for OMNIA 4.5 After Running the .iso

Create a Site Lockdown Input for OMNIA

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

Creating Operator Profiles

Creating Relay Actions I/O in OMNIA

Deleting Tag Holders in OMNIA

Omnia Lite

Convert a Nexus Lite Database into OMNIA Lite Database

OMNIA LiTE Backup

PM Tronics Hardware

Amano Readers and Credentials

Change Modulation mode on XQT904 Quad Transmitter
How do I change Wiegand Output Mode on Amano readers?

Legacy Hardware

Factory Reset legacy Amano IP Cameras (sold prior to 2018)

Factory Reset Nexus220 controller

How do I factory reset the EC2 (400i) controller?

Setting IP on PMTronics Inc. Access Control Hardware

Partner Products

Partner Products

IDEMIA Sigma Lite Readers NOT compatible for use in AmanoNet or Nexus220

Setting Read Range on a Conekt Reader

Video Management Systems

Cathexis Video (Amano Vision)

Cathexis Video AV (AntiVirus Exceptions)

AmanoDVMS

Which AmanoDVMS ports need to be open on my firewall?

Vision

AmanoVision web access user name case sensitivity usage

  • « Go to Previous Page
  • Page 1
  • Page 2
  • Page 3
  • Page 4
  • Interim pages omitted …
  • Page 9
  • Go to Next Page »

PMT Security

Copyright © 2025 PMT Security, Inc. | All Rights Reserved