Supported ESSL models and connection methods
| Method | How it works |
|---|---|
| ADMS push over HTTP | The terminal sends each punch to Ankastra the moment it is recorded |
| SDK pull | For older models without ADMS, punches are read from the terminal over the local network |
Supported ESSL models include the X990, X628, iFace302, U-Face 602, MB20 and G3 Plus.
How the connection is set up
- Sort the terminals by model. Our onboarding team checks which of your ESSL terminals can use ADMS push and which older units have to be read through the SDK, before anything changes on site.
- Turn on ADMS push. On each terminal that supports it, enter the server address we give you in the network or cloud server settings. Menu names vary by firmware.
- Stop the manual exports. Once a terminal pushes, its punches arrive with the unit, the department and the verify mode attached, so nobody downloads logs from the terminal or from a site PC.
- Match device users to employees. ESSL user IDs are mapped to the Ankastra roster, contract workers included.
- Run both side by side. Compare Ankastra's attendance against your current ESSL reports before you switch the old process off.
Our onboarding team does this with you.
If your ESSL data lives on one PC
A common ESSL setup has the terminals reporting to attendance software on a single computer at the site. That works until the computer is switched off over a weekend, the database is not backed up, or head office needs the numbers before someone at the plant exports them.
With ADMS push, the terminal reports to Ankastra directly. Attendance is available wherever HR works, every edit is logged, and there is no site PC to look after.
ESSL in a worked scenario
The modelled scenario for a 220 employee auto components plant starts with four ESSL terminals across two units, each exporting its own log into a shared spreadsheet, and night shift punches corrected by hand every day. Switching the terminals to ADMS push and letting shift rules handle punches that cross midnight is part of how HR admin falls from 104 hours a month to 16 in that model. Every input is printed on the page, so you can redo the sums for your own terminals.
After the punch
From there every brand is handled the same way: shift rules, exceptions and the muster roll, contract workers on the same roster, with attendance reconciled against the contractor's bill, and statutory payroll from the same punches in the Pro plan.
Plan and price
Device integration is in the Growth plan: ₹5,999 a month for 50 employees, or ₹5,099 a month billed annually, plus GST. Each employee above 50 adds ₹49 a month.
ESSL is a trademark of its owner. Ankastra reads attendance from ESSL devices; it is not made, sold or endorsed by ESSL.
Questions people ask
Do we need to replace our ESSL devices?
No. Your X990, iFace302, MB20 and other ESSL terminals stay on the wall. Ankastra reads them over ADMS push, or through the SDK on older models.
Will punches be lost if the internet goes down?
No. ESSL terminals buffer punches internally, so anything recorded during an outage is held on the device and delivered when it reconnects.
Can Ankastra read ESSL devices across several plants?
Yes. Each terminal is mapped to its unit, so attendance is reported unit-wise and rolled up across plants, with multi-location roll-ups included from Growth.