An engineering consultancy left Excel for one system across projects, HR and purchasing.
An engineering and technical consultancy has five offices across Iraq, Egypt and Lebanon. Before this project the firm ran on Excel. We implemented Odoo for it and wrote the link between its fingerprint terminals, attendance and timesheets.
Five offices, followed in Excel.
The firm's projects run through design and planning, tendering and supervision, with staff in several countries. All of it was followed by hand in Excel, with no live view of a project or a team.
From the fingerprint to the timesheet.
The scope covered projects, timesheets, HR, payroll, purchasing and accounting. Projects move through five stages, from initiation to closure. Working hours are set per office: nine hours a day over five days in Cairo, eight hours over six days in Baghdad.
The part we wrote ourselves is the attendance link. Each scan on a fingerprint terminal is stored as it arrives, matched to an employee and turned into that person's day, from first scan to last. The weekly timesheet then shows those attendance hours beside the hours logged on projects.
- Fingerprint terminalsThe terminals push every scan to the system as it happens, and each scan is kept as received.
- Single-scan daysA day with only one scan is closed automatically with that day's scheduled hours.
- Attendance by handAttendance entered on the web waits for a manager's approval before it counts.
- Timesheets beside attendanceAttendance hours sit next to logged hours in the weekly grid, by project and task.
- Terminal clocksThe server keeps the terminals on Cairo time and corrects them when summer time changes.
- OvertimeOvertime is calculated from attendance by the rule set on each employee's contract.
- Time offLeave requests are approved in two steps: first the manager, then HR.
- Purchase approvalsA purchase request passes the team leader, the purchasing manager and the director.
- Odoo 19
- Python
- PostgreSQL
- ZKTeco