Does AionHRMS work with eSSL X990?

The X990 is an iClock/ADMS candidate, but the model name alone is not a deployment guarantee. Send the serial, firmware and a photo of its Comm/ADMS server settings. We confirm registration and a test punch before recommending a cutover.

Does it work with ZKTeco devices?

Compatible ZKTeco terminals using the implemented iClock/ADMS dialect can work. Send the exact model, serial and firmware; we confirm its server settings and a test punch before rollout.

Does it work with Realtime biometric machines?

AionHRMS implements Realtime's native protocol directly. Exact model support still requires confirmation and a test punch. Realtime biometrics are enrolled at the terminal rather than pushed as templates from AionHRMS.

Will repointing the device erase the fingerprints already enrolled on it?

Changing only the server address normally does not clear templates already stored on the terminal, but verify the procedure for the exact firmware before making a change. After connection, compatible iClock templates can be stored centrally and re-pushed to compatible iClock devices. Realtime biometric enrolment is completed at each terminal.

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.

Integration directory

Biometric attendance device integrations

Start with the machine already mounted at your gate. We confirm its model, firmware and communication mode before recommending any migration or replacement.

AionHRMS supports two implemented device-protocol families: iClock/ADMS for confirmed eSSL and ZKTeco models, and a native Realtime protocol for confirmed Realtime models. CP Plus compatibility is model-dependent. Every approval requires the exact model, firmware or serial evidence, server-setting confirmation and a successful test punch. One account can combine confirmed devices for attendance, but biometric-template reuse is never assumed across brands.

eSSL / eTimeTrackLite

Confirm an iClock/ADMS-capable model, repoint it safely and keep the existing hardware where it passes a test punch.

See eSSL integration

ZKTeco

Review the exact terminal against its cloud-server settings; model names alone are not accepted as compatibility evidence.

See ZKTeco integration

Realtime Biometrics

Use AionHRMS's implemented Realtime protocol on confirmed models; biometric enrolment remains at the terminal.

See Realtime integration

CP Plus

A candidate integration only where the exact device exposes a compatible ADMS mode. We confirm it before purchase or cutover.

Check CP Plus

ADMS repoint configurator

Pick your brand and get the menu path to the cloud-server screen, every field to set, and what each one silently breaks when it is wrong.

Open the configurator

Use your existing machine

Yes, no or test-first, by brand: what carries over when you switch software, what does not, and how the attendance PC is retired.

Read the guide

Connect an eSSL machine

The full repointing walkthrough: the communication menu, the ADMS screen, the fields to set and the test punch that proves it.

Follow the steps

Attendance API

Send clean attendance events into an ERP, payroll workflow or authorised AI agent without exposing biometric templates.

Review API options

How to tell whether your terminal will work

The brand on the front is not enough. Look for Comm, Network, Cloud Server, ADMS or Server Settings and collect the exact model, serial or firmware plus a settings photo. A configurable server address is useful evidence, but support is confirmed only after the protocol handshake and a test punch succeed.

Find Comm / Network / ADMS / Cloud Server in the device menu
If you can set a server address and port, it is a candidate for repointing
The device normally 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
Re-push compatible iClock templates to compatible iClock terminals; Realtime biometrics are enrolled at the 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

Mixed terminal estates are common when hardware is bought over several years, inherited through an acquisition or sourced from different local dealers. AionHRMS is designed for this scenario, but each device still needs a model-and-firmware compatibility check. Ask manufacturer-cloud vendors whether they accept third-party brands and obtain the supported-model list in writing.

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

Protocol and enrolment compatibility matrix

This matrix describes implemented server behavior, not blanket support for every device carrying a brand. The written confirmation for a rollout names the exact model and firmware.

Capability	iClock / ADMS	Realtime native
Candidate brands	eSSL, ZKTeco and other terminals that expose compatible iClock/ADMS server push.	Realtime models using the implemented native protocol.
Punch ingestion	Implemented; validated with a live test punch on the candidate model.	Implemented; validated with a live test punch on the candidate model.
Employee profile push	Implemented for compatible command dialects.	Implemented; remote enrolment command opens the device workflow.
Biometric reuse	Compatible templates can be stored and re-pushed only where source and target formats agree.	No central biometric-template push; enrol the biometric at each Realtime terminal.
Face/photo handling	Model-specific; some photo-capable terminals accept an employee profile photo.	Confirmed during model review; not represented as cross-brand template sync.
Confirmation evidence	Model, serial, firmware, server-setting screenshot and successful test punch.	Model, serial, firmware, protocol check and successful test punch.

Frequently asked questions

Does AionHRMS work with eSSL X990?: The X990 is an iClock/ADMS candidate, but the model name alone is not a deployment guarantee. Send the serial, firmware and a photo of its Comm/ADMS server settings. We confirm registration and a test punch before recommending a cutover.
Does it work with ZKTeco devices?: Compatible ZKTeco terminals using the implemented iClock/ADMS dialect can work. Send the exact model, serial and firmware; we confirm its server settings and a test punch before rollout.
Does it work with Realtime biometric machines?: AionHRMS implements Realtime's native protocol directly. Exact model support still requires confirmation and a test punch. Realtime biometrics are enrolled at the terminal rather than pushed as templates from AionHRMS.
Will repointing the device erase the fingerprints already enrolled on it?: Changing only the server address normally does not clear templates already stored on the terminal, but verify the procedure for the exact firmware before making a change. After connection, compatible iClock templates can be stored centrally and re-pushed to compatible iClock devices. Realtime biometric enrolment is completed at each terminal.
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.

Need an answer for your exact device and sites?

Send the model, firmware or serial details. We confirm compatibility before a quote.

Check compatibility