Unigaz Case Study: Multi-Country Attendance with OrangeHRM
Case study of how Unigaz connected biometric devices in multiple countries to OrangeHRM through the Cams Biometrics Web API, with timeline and results.
Case study of how Unigaz connected biometric devices in multiple countries to OrangeHRM through the Cams Biometrics Web API, with timeline and results.
Why proprietary protocols and SDKs lock biometric device buyers in, the three lock-in layers, and how protocol adapters and open REST APIs remove them.
Step-by-step server settings for Cams Biometrics and other-brand biometric devices to connect online: menu path, domain, port and approval options.
In most organisations, the door and the time clock are two different systems. Security owns access control. HR owns attendance tracking. Each has its own devices, its own enrolment process, its own database, and its own idea of who is in the building. Yet both are answering versions of the same question: who is this…
Biometric devices that restart repeatedly often have a weak power adapter. Learn the 12V-2A and 12V-4A adapter recommendations and what to do next.
Connect a biometric device to the network by LAN or Wi-Fi, whitelist the server IPs and domains, set the server address and port, and troubleshoot.
Compares the Cams Biometric API with SDK-based and other biometric integration methods: real-time push, two-way user management, and no port forwarding.
Explains protocol adapter architecture for biometric devices: how SDKs decode device protocols, four adapter layers, cloud needs and SDK migration.
How Cams Biometrics sets IN/OUT punch states: device-level selection, Actual, First In Rest Out and ZigZag modes, and limits such as 24-hour punch history.
How the Cams GymBio34 terminal and its REST API automate gym membership access: remote enrollment, subscription dates, time windows and disabling users.