This guide is intended for HR teams, IT teams, and implementation stakeholders.
How Anviz Clocks Work
Anviz clocks do not connect directly to Sense HR.
Clock events are sent through the Sense Clock Transactions Service, which is installed on a Windows device within your network. It acts as the bridge between your Anviz clocks and Sense HR.
Anviz Clock → Local Network → Sense Clock Transactions Service (Windows PC) → Sense HR
Network Checklist
Confirm:
☐ The clocks and Windows device can be connected to the same network
☐ Devices can communicate with each other directly
☐ Clocks are not on a guest Wi-Fi network
☐ Clocks and the Windows device are not separated by VLANs or network isolation policies
☐ Internal firewalls or endpoint protection will not block local communication
☐ Wi-Fi signal is reliable at the planned clock locations
Internet and Firewall Checklist
The Sense Clock Transactions Service (Windows PC) must communicate with Sense HR through Azure IoT Hub.
Ask your IT team to allow outbound access to:
☐ TCP port 8883
☐ TCP port 443
☐ TCP port 80 — may be required for certificate validation
☐ devices-iothub6b4a7fb.azure-devices.net
If your organisation uses DPI, SSL inspection, certificate filtering, or application-aware firewalls, additional configuration may be required.
Windows Device Checklist
Confirm a Windows device is available that:
☐ Can remain powered on during normal operations
☐ Has administrator access available
☐ Has internet access
☐ Can install and run the Sense Clock Transactions Service (Windows PC)
☐ Can communicate with all planned clock devices
During implementation, the following will also be required:
Sense Clock Transactions Service
Microsoft .NET Runtime 10 — x86 and x64
Installation Location Checklist
Confirm each planned clock location:
☐ Is easily accessible to employees
☐ Has a suitable power source nearby
☐ Has reliable network coverage
☐ Is free from excessive dust, moisture, or direct sunlight
☐ Is not near equipment that may cause electrical interference
☐ Is not in an area where the device may be damaged accidentally
Building and Signal Considerations
Wi-Fi performance may be reduced by:
Thick concrete walls
Metal-clad buildings
Warehouses with racking
Plant rooms or service areas
Areas with poor wireless coverage
Heavy machinery or electrical interference
Where Wi-Fi coverage is uncertain, a wired network connection is recommended.
Multi-Clock Installations
If multiple clocks are planned, confirm:
☐ Every clock can communicate with the Windows device running the Sense Clock Transactions Service
☐ Reliable network connectivity is available at every clock location
☐ Power and network access are available for each device
Biometric Considerations
If using fingerprint or face recognition, consider whether the working environment may affect authentication.
Examples include:
Employees wearing gloves
Dirty, dusty, or wet working conditions
Heavy manual work or chemical exposure
Strong sunlight or poor lighting near face recognition devices
In these environments, RFID / NFC card authentication may be more reliable.
Discuss With Your IT Team
Before ordering, ask your IT team to review:
Network setup
Firewall rules
Internet access restrictions
Device communication requirements
Proposed installation locations
Completing these checks before implementation helps avoid delays during setup.