Brain Station 23 | Odoo ERP Implementation Case Study
Brain Station 23 built a custom attendance management system on Odoo Community 15 that connects planned schedules, RFID access-control punches and reporting for Augmedix Bangladesh.
Founded in 2012 and headquartered in Dhaka, Augmedix Bangladesh employs between 500 and 1,000 people. It is the Bangladesh operation of Augmedix, a healthcare technology company that streamlines clinical documentation. Technology, including artificial intelligence, is combined with a team of documentation specialists (MDS) who support physicians in the U.S. healthcare system from Bangladesh.
As operations matured, a planned, shift-based workforce needed a dedicated system for workforce planning and accountability. Leadership identified the need for an attendance management system that connects planned schedules, actual presence and reporting in one place.
Planned schedules, actual presence captured by RFID access-control devices, and the rules for lateness, breaks and overtime were not brought together in a single system. Augmedix Bangladesh already operated RFID infrastructure through its DSS access-control platform; the goal was to build on it rather than replace it.
Augmedix Bangladesh chose Odoo for its attendance management system, with Brain Station 23 as implementation partner. Leadership wanted transparency over planned schedules, attendance data to support performance evaluation and accountability, and more efficient HR and payroll processes with less manual entry.
Brain Station 23 held structured requirements workshops with HR and operations stakeholders, documented the findings in a Software Requirement Specification and obtained formal approval. Early concerns were user adoption, reliable connectivity to the access-control devices, and trust in the calculated results.
The project began in October 2023. After a gap analysis of standard Odoo, targeted customizations were built while keeping the familiar Odoo Community interface. The access-control integration was treated as a research task, so the best way to connect to DSS was validated before the design was committed.
Odoo connects to the DSS access-control platform via API, with automatic scheduled synchronization and on-demand refresh. Approved changes made in Odoo can be pushed back to DSS.
Before: Planned check-in and check-out times were not held in a validated schedule linked to attendance.
After: A master Attendance Plan records planned times per employee, imported from Excel or entered manually. Duplicates and overlaps are blocked, and leave can be marked on the plan.
One validated source of planned schedules that every attendance calculation is measured against.
Before: Devices recorded presence on the DSS platform, with no automatic comparison against planned shifts.
After: Punches are pulled into Odoo every 10 minutes and stored, then compared with each employee's planned device and time window.
Every punch is processed automatically into a single attendance register.
Before: Sign-in buffers, pre-shift time, breaks and overtime had to be applied consistently by hand.
After: Working time, break allowance and sign-in buffer are configurable. The engine calculates working time, break time, overtime and early-exit time per employee per day.
Transparent, repeatable calculations that HR and payroll can rely on.
Before: Card and device-access changes were handled in the access-control platform, with no link to employee records.
After: Employee, RFID and device-access details are synchronized into Odoo. Authorized users change cards or devices through a dedicated form and push the change to DSS, so two cards are never active at once.
One governed workflow for access changes, aligned with employee records.
Before: Attendance insights were not available as consolidated dashboards or a master register.
After: Dashboards cover absent MDS, early arrivals, on-time punches, late arrivals, and room capacity versus occupancy, alongside a master register with filtering, grouping and export, scoped by user role.
Management and HR see attendance trends at a glance and can act early on patterns such as absenteeism.
Punch data synchronizes every ten minutes. Seven categories of attendance conditions are calculated against each employee's plan, and five dashboard views plus a master register with more than twenty processed fields serve as a single source of truth in any time zone.
Operations leaders and HR see present, absent, early, late and on-time employees on one dashboard.
Planned and actual attendance are compared automatically, and lateness, early exits and excessive breaks are calculated transparently.
Attendance and absenteeism trends are visible in dashboards and a filterable register, so managers can act early.
Accurate, processed attendance data reduces manual entry and calculation errors.
Working time, break allowance, sign-in buffer and early-exit threshold are configurable, and plans are bulk-imported, so the same rules extend to new employees and devices.
All punches are stored, work hours, breaks and early exits are traceable by time stamp, and three role levels (Super Admin, Ops Admin, HR Admin) protect sensitive data.