Optimización de la máquina de tarjetas de tiempo

In enterprise IT, we often think software solves everything. But when you are dealing with a manufacturing floor, the physical environment will destroy your software within days.

I was recently contracted to fix a broken HR clock-in system for a manufacturing plant with 40 employees. The problem was not the HR software itself — it was the physical reality of the factory floor.

The Problem: The "Glove Penalty"

Plant employees wear heavy-duty industrial safety gloves. The legacy clock-in system relied on standard PVC ID cards.

Here is what the physical UX looked like at 6:00 AM every morning:

1. An employee walks up to the time clock.
2. They remove their industrial safety gloves.
3. They dig through their pockets to find their wallet.
4. They pull out their ID badge (trying to keep it inside the wallet so it doesn't get coated in industrial grease).
5. They scan the badge, put it away, and put their gloves back on.

This took approximately 60–90 seconds per employee. Multiply that by 40 employees, twice a day (clock-in and clock-out), and the plant was bleeding over an hour of pure production time every shift change — just standing at the terminal.

Management initially tried to solve this by printing QR codes and sticking them to employee helmets or equipment. Within two weeks, industrial washing processes and factory grease rendered the QR codes completely unreadable. On top of that, QR codes are a massive security failure: anyone can take a photo of a QR code and "punch in" for their friend.

The Solution: Zero-Friction NFC Under the Glove

I completely scrapped the ID cards and QR codes and moved to ruggedized silicone NFC wristbands.

Here is why this completely changed the operational flow:

• Zero Exposure Clock-In: Employees wear the NFC wristband under their heavy industrial gloves. Because NFC (Near Field Communication) uses radio frequencies, it penetrates thick fabric and glove rubber.
• The New UX: The employee walks up to the terminal, taps their gloved wrist against the reader, hears a beep, and walks to the floor. Time elapsed: 1.5 seconds.
• Indestructible: NTAG chips are hermetically sealed inside the silicone wristband. They survive industrial washing, chemical exposure, and heavy physical impact. They cannot be washed off like a QR code.
• Anti-Buddy-Punch: Every NFC chip has a hardcoded, locked UID. You cannot "photocopy" an NFC chip with a smartphone camera.

The Architecture: A Custom Odoo HR Module

I didn't want to rely on complicated third-party webhooks, Zapier integrations, or external middleware. I wanted this to be a seamless, native experience for the HR department directly inside their existing ERP system.

To accomplish this, I engineered a custom Odoo module that extended the native hr.employee framework.

Here is exactly how I built it:

1. Extending the Employee Profile: I wrote a custom Python model to inject a dedicated nfc_uid field directly into Odoo's employee form view.
2. The "Pair NFC" Action Button: I created a custom action button directly in the employee profile interface inside Odoo. When HR issues a new wristband, they simply click "Assign NFC," tap the wristband to the USB reader on their desk, and the unique NFC ID is permanently linked to that employee's database record.
3. The Kiosk Integration: I overrode Odoo's native attendance kiosk mode. Instead of requiring employees to enter a PIN or scan a barcode using a camera, the kiosk simply listens for NFC keyboard input.

When the employee taps their wrist against the NFC reader on the plant floor tablet, the reader instantly passes the UID string to Odoo. My custom module intercepts the string, queries the hr.employee database to find the matching nfc_uid, and automatically generates the hr.attendance clock-in/clock-out timestamp.

The Takeaway

Good engineering is not just about writing clean Python code — it is about understanding the physical constraints of your user. By eliminating the need to remove an industrial glove, we did not just save the company thousands of dollars in lost operational time: we removed a daily frustration for 40 hardworking employees, all managed natively inside Odoo.

Related Reading:

The "Kill the Clipboard" CMS Mandate ➔

Architecting the Aura Human Operating System ➔

The Poison Pill Architecture — Zero-Knowledge Security ➔

Stop Hiring Developers. Hire an Orchestrator. ➔

Humanos Foundation — The Mission Behind the Architecture ➔