PMT Security

Advanced Access Control

OMNIA

Batch Operations OMNIA

Batch Operations OMNIA

The Batch Operations allows an End User to perform bulk operations in regards to tagholders. This process can be used to enroll people/assets in large numbers rather than one at a time. This tool can also be used to update multiple people/assets at the same time as well as the ability to update tagholders to different access groups. 

You will want to use this process to add an access group to a group of tagholders.

Go to enrollment > Batch Operations

Select the type of Batch Operation and What to Update

Select the records that need to be updated

Choose what to update

Select/de-select access groups:

Select the Action wanted for the Access Groups

Review the summary and EXECUTE

You will get a confirmation pane along with a log file detailing the changes.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Running OMNIA as a Service

Running OMNIA as a Service

OMNIA can run as a service that will start up automatically when your system boots up. 

OMNIA can run as a service that will start up automatically when your system boots up. 

When running OMNIA as a service, the server application will not be available. 

To use the server application when OMNIA is running as a service, you will need to stop the service and then open the server application.

NOTE: You can not run the OMNIA application while the service is running. Running them concurrently could cause irreversible database corruption.

Configuration:

There is a batch file in the OMNIA folder that will configure OMNIA to run as a service. This batch file needs to be run from the command prompt as an administrator.

1. Close the OMNIA server application by right-clicking the OMNIA icon in the system tray>Exit

2. Run CMD as admin (C:\windows\system32>Right-click CMD>Run as administrator)

3. Navigate to the OMNIA  directory.

     type cd /. press Enter

     type cd OMNIA press Enter

     type cd 4.6.5.1703.62798 press enter

     type install.OMNIA64.Servcie.bat press enter

                    Installation takes place instantly.

5. Close CMD

Go to services and set the OMNIA64service to Automatic Delayed Start

  1. In Services, Right Click OMNIAServer x64
  2. Select Properties
  3. Use the dropdown to select Automatic (Delayed Start)
  4. Select OK
  5. Start the OMNIA Service

To uninstall the service, follow the same steps, but instead execute the uninstall.OMNIA64.service.bat file

WARNING

The only time when OMNIA can run as a service is when the hardware has completely been commissioned, because the server application will be unavailable. If the Server App needs to be accessed, stop the service before starting the server app. Running the service along with the server app can break your database

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Lockout Delay and Timed Anti-Passback

Lockout Delay and Timed Anti-Passback

Entry and Exit Lockout Delay is a feature that will disallow multiple reads at the same reader within a certain period of time.  In Amano systems, this feature allows you set a timed delay period (in minutes) per zone and reader position during which the system will enforce restrictions after the presentation of a Tag. This feature prevents multiple presentations of a Tag to the same reader during the set delay period.

NOTE:  This feature is only available on zones setup with APB set to Relaxed or Strict. 

Setting Entry or Exit Lockout Delay

  • From the main menu select Setup >  System > Zones.
  • Select or create your Zone.
  • In the settings section of the Zone, indicate the Entry or Exit lockout delay of your choosing (in minutes)

Allow the system a few moments to synchronize.  Anyone presenting their tag to a reader within this zone where the entry or exit lockout delay is set, will start the clock on that particular tag.  You will then need to wait until the time expires before you can present again.

Normally you would have at least one entry and one exit reader on a zone to allow for the system to account for the tagholder’s position relative to the zone.  (inside or outside zone)

However, you can utilize this feature with one reader if you are allowing free egress on a zone, but still want to have some control over the tag usage on the ingress.  It is a bit counter intuitive, but we provide the instructions below.

Timed APB using only one reader – OMNIA

  • From the main menu select Setup >  System > Zones
  • From the Zones view, you may add a new Zone by selecting the plus icon at the top right of the page.
    NOTE: You may choose to configure an existing zone.
  • Enter a Zone Name
  • Choose the System Controller.
    NOTE: Zones are tied to a single system controller.  
  • Under Settings set Anti-Passback to “Relaxed”
  • Set Exit Lockout Delay enter the required time in minutes

Setup the Door:

  • From the main menu select Setup > System > Doors

From the Doors page add a new Door by selecting the “+” button on the top right of the page and Name the Door or Choose a Door that has already been created.

  • Under “Settings” Select the Zone you created earlier (APB)
  • Under “Settings” select the reader to be uses as the Exit Reader
  • Note: For this to work correctly this reader MUST be configured as an Exit Reader and will NOT work if set as an Entry Reader

On every allowed event, the transaction viewer will display “Allowed APB Violation Out” and grant access.  During the Exit Lockout Delay access will not be granted and the transaction viewer will display “Denied APB Out”

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

OMNIA 4.x – Requirements Specification

OMNIA 4.x – Requirements Specification

Hardware and Software Minimum Requirements

Hardware Minimum Requirements

OMNIA Server

  • Processor: Intel Xeon Processor (or equivalent); i7, i9 also acceptable.
  • RAM: 16 GB (32GB Preferred)
  • Available disk space: 200 GB
  • Screen resolution: 1280 × 800

OMNIA Client

  • Intel Core i5 Processor (or equivalent)
  • 8GB RAM
  • 10GB available disk space
  • USB 2.0 Port(s) for MDE and/or Biometric Enrollment Devices

Software Minimum Requirements

OMNIA Server

  • Microsoft Windows 10 Professional (Windows Server 2016 or better recommended)
  • Microsoft SQL Server 2019 Express with Advanced Services (Included with Installer)
  • Local administrator rights

OMNIA Client

  • Microsoft Windows 10 Professional
  • HTML 5 Compliant Browser (Mozilla Firefox or Google Chrome recommended)
  • Local administrator right required when printing tags or utilizing USB tag and biometric enrollment devices

NOTE:  You may use an HTML5 compliant web browser on the same computer running the server application to connect to the OMNIA client. When connecting via a remote computer, see the network requirements section below.

Network Requirements

See KB article on Best Practices which includes network port listing for firewalls and routing.

Network Configuration – Best Practices

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems

Basic Trouble Shooting OMNIA

Basic Trouble Shooting OMNIA

This article will cover some basic troubleshooting techniques.

I can’t log in to OMNIA

Ensure that the OMNIA Engine is running on the Access Server. To launch the portal base app, go to C:\OMNIA\Bin\OMNIA.exe  Right Click and Run as Administrator in the Web Browser. 

Ensure that you enter the correct address for the server in URL in the browser. Followed by the correct port number.

Ensure that you are using the correct username and password. Remember that the password is CASE sensitive.

Ensure the OMNIA Engine icon is visible in the system tray of the OMNIA application server (PC or server that has the OMNIA application installed.)

I can’t scan a Tag or enroll finger print. The option is Missing?

Is your device plugged into the USB Port?

Plugins Manager

In order to use a USB device in a browser, certain plugins are required. OMNIA uses a program called Plugins Manager to make things easy for you.

Ensure that the Plugins Manager is running in your task bar, and that the peripheral you are using has a green dot.

If you don’t see the Plugins Manager, launch it from C:\OMNIA\Client\ClientInstall.OMNIA.Plugins.exe or it can be found in the OMNIA Software. In the Setup Tab/General/Downloads.

MDE is plugged in and installed, but it does not turn green in Plugins Manager

(The dot in plugins manager stays blue)

It’s likely that windows has issued the incorrect driver during installation. This can easily be fixed by changing the driver in device manager. The correct driver is named MDE USB VCom Port

Steps to change MDE driver:

  • Open device manager
  • Open Ports (COM&LPT)
  • Right-Click on USB Serial Device
  • Click Update Driver
  • Select Browse my computer for driver software
  • Let me pick from a list of available drivers on my computer
  • Select MDE driver > Next > Close

Tag/Finger does not open door

Using Events to Troubleshoot (Found in Dashboard >Transactions)

The Transaction page is a great place to do basic troubleshooting. When Tags don’t work, look at the event to determine the cause.

NOTE: On busy sites the transactions page might move too fast to see the problem event. In this case, run a Transaction Report on the Tagholder to see their latest events.

Here follows a list of denied events and their meaning…

Denied Location

Tag does not have access to that door.

Option 1 Select an Access Group in the Tagholders’ configuration page that includes that door.

Option 2 (Caution) Modify the assigned Access Group to include the desired door.

WARNING: Making changes to the area will affect all Tagholders using it.

Denied Time or Day

Tagholder’s access group does not include the time or day.

Option 1 Look at Enrollment > Access Time Patterns to adjust times/days, or grant the Tagholder an access group that contains a valid time pattern.

Option 2 Use the Show Edit Mode option found in Access Groups to see times assigned to the area, you can also make any required changes.

WARNING: Making changes to the access time pattern will affect all Tagholders using it.

Holidays can also cause denied time or day events. See if any holidays have been entered on the day of the denied event.

Denied APB

Tagholder needs to follow the rules of anti-pass-back (APB).

It is possible to override APB for individual Tagholders under Advanced in the Tagholder configuration. (Not Recommended)

Denied Tag Suspended

Tag is suspended.

Open the Tag under the Tagholders configuration and set the Tag Status to Normal.

Denied Tag Expired

Tag has an expiry date entered. Configure expiry dates under the Tagholders configuration.

Denied Location Locked

The default mode on the reader is set to Locked Or, there is a Device Time Pattern locking the reader.

Contact the system administrator.

Denied Pin

The default mode on the reader is set to Card with Pin, OR, there is a Device Time Pattern enforcing Tag with Pin.

During this mode, users need to enter a pin code AFTER presenting their credentials (There will be a short beep alerting you to enter a pin)

Pins can be assigned under the Advanced section in the Tagholder configuration.

Denied Unknown Tag:

Here are a few possible reasons for denied unknown tag events.

Denied unknown tag, and there is no name.

Tag has not been assigned to a Tagholder (New Tag)

Denied unknown tag, and there is a name.

The tag is assigned to the person but;

  • They don’t have an access group assigned (Assign at least one access Group)
  • The controller needs to sync (See Next Section)
  • The Tagholder is non-current (Ensure that the current tick is active under Advanced in the Tagholders configuration page)

Controller Sync

To ensure that all Tagholders are loaded onto the hardware, perform a sync under Setup > Services

Either select All Devices, or select individual controllers.

WARNING: Synchronizing your controllers will disable its Tag readers for a short while. Please plan accordingly

Not getting any transactions

Controller might be offline.

Auto sync might be disabled

OMNIA Engine might not be running on the OMNIA server.

Contact the Administrator.

Need further assistance?

Submit a Support Ticket

Submit a Support Ticket

FAQ

Access Control

PM Tronics Hardware

Partner Products

Video Management Systems