Device compatibility

Cloud software for eSSL, ZKTeco and Realtime — in one system

The single question every dealer-referred buyer asks first is whether it works with the machine they already have. Usually it does. Here is exactly what is supported and how to check your own model before you spend anything.

Get started Talk to sales

AionHRMS supports biometric terminals that push attendance to a server, which covers the large majority of devices sold in India. Two protocols are implemented: iClock/ADMS — the push protocol used by most eSSL and ZKTeco terminals, and by other manufacturers speaking standard ADMS — and Realtime's native protocol, implemented directly rather than through an adapter. Crucially both work in the same account, so an eSSL reader at the head office and a Realtime terminal at the plant report into one attendance register, which no manufacturer's own cloud will do.

iClock / ADMS

the eSSL and ZKTeco mainstream, including X990-class terminals

Realtime

native support for Realtime's own push protocol

One account

both protocols side by side, sharing one employee list

Payroll behind it

shifts, late rules and salary from the same punches

How to tell whether your terminal will work

The deciding factor is not the brand on the front — it is whether the device can push records to a server address you control. Look in the terminal's settings menu for an option named Comm, Network, Cloud Server, ADMS or Server Settings. If there is a field for a server address or domain and a port, the device is almost certainly supported.

  • Find Comm / Network / ADMS / Cloud Server in the device menu
  • If you can set a server address and port, it can be repointed to us
  • The device keeps its existing fingerprint and face enrolments during a repoint
  • Send us the model and serial number and we will confirm before you commit

What we can do to a device, not just read from it

Reading punches is the easy half. The part that saves real time is pushing instructions back to the terminal, which is what turns a cloud dashboard into something that controls the door rather than just describing it.

  • Push employee records to the device from the browser — no keypad entry
  • Push stored fingerprint and face templates so nobody re-scans on a second terminal
  • Block and unblock an individual's access across every device at a site
  • Push a profile photo to terminals that display one at verification
  • Sync device time, and trigger live enrolment capture at the terminal
  • Remove a stale user record left behind by an earlier system

Mixed estates are the normal case

Almost no organisation with more than two sites has a single brand of terminal. Hardware is bought over years, from whichever dealer was nearest, and inherited through acquisitions and office moves. Manufacturer clouds treat this as an unsupported configuration. We treat it as the default one.

  • Different brands at different sites, in one account and one register
  • Different brands at the same site, sharing one employee list
  • Adding a terminal from a new manufacturer changes nothing operationally
  • Attendance is computed server-side, so it is comparable across all of them

Verification methods

What a terminal can verify depends on the terminal, not on us. AionHRMS records whichever method was used for each punch, so mixed workforces can be handled without excluding anyone from the register.

  • Fingerprint — the most common, lowest cost per terminal
  • Face recognition — faster and contactless, better at busy entrances
  • RFID / proximity card — the practical answer for worn fingerprints
  • PIN — a fallback, and multi-factor where the device supports it

Manufacturer cloud versus a brand-neutral one

Manufacturer software is genuinely fine for a single-brand, single-site customer. The comparison only matters once that stops being true.

AionHRMSManufacturer's own cloud
Device brandseSSL, ZKTeco and Realtime together.That manufacturer's devices only.
Mixed siteSupported and expected.Requires a second system.
Cost modelPaid subscription, sold through your dealer.Often free, or bundled with new-device purchase.
If you switch hardware brandNothing changes.You migrate to a different platform.
Template portabilityTemplates stored centrally and re-pushed to any supported device.Typically confined to that brand's ecosystem.

Frequently asked questions

Does AionHRMS work with eSSL X990?
Yes. The X990 and other eSSL terminals using the iClock/ADMS push protocol are supported. Point the device at our server from its Comm/ADMS settings menu and it will register itself on the next poll.
Does it work with ZKTeco devices?
Yes, for ZKTeco terminals that speak the iClock/ADMS push protocol, which covers most current models. Send us the model number to confirm your specific unit.
Does it work with Realtime biometric machines?
Yes — Realtime's native protocol is supported directly rather than through an adapter, so Realtime terminals work alongside eSSL and ZKTeco units in the same account.
Will repointing the device erase the fingerprints already enrolled on it?
No. Changing the server address does not clear the device's stored templates. Existing enrolments remain on the terminal and keep working. Templates captured after the repoint are additionally stored centrally, so they can be pushed to your other terminals.
My terminal is from a brand you have not listed. What now?
Send us the make, model and serial number. If it speaks the standard ADMS push protocol we can very likely take it, whatever the badge on the front says. If it genuinely cannot push to a server address you control, we will tell you so rather than sell you something that will not work.
Can I keep using the manufacturer's software at the same time?
Generally a terminal pushes to one server at a time, so in practice you choose one. Migrating is straightforward, but plan it deliberately rather than assuming both will run in parallel.

Related

Send us your model number

We will confirm compatibility before you spend anything on hardware or software.

Get started Talk to sales