A made-to-order Odoo module delivering an employee attendance calendar, monthly summaries, and an advanced HR analytics dashboard. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19 database. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $249.00 USD; request a quote for a scoped proposal.
アプリマニフェスト
あなたのワークフローに合わせて構築
A made-to-order Odoo module delivering an employee attendance calendar, monthly summaries, and an advanced HR analytics dashboard. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19 database.
自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。
一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。
ECOSIRE がお客様の Odoo 上で構築・設定・インストールします。
約2〜4週間で稼働し、リリース後のサポート期間が付きます。
Most HR teams running Odoo hit the same wall: the native Attendances app records raw check-in/check-out pairs, but managers actually need to see patterns — who is chronically late, how many hours each person logged this month, which days had gaps, and how a department trends over a quarter. Out of the box that means exporting hr.attendance records to a spreadsheet, hand-building pivots, and repeating the exercise every pay cycle. The calendar view that would answer "what did March look like for this employee" simply is not there, and the stock pivot and graph views do not give leadership a single glanceable HR dashboard.
Attendance Dashboard Advanced is a build-to-order Odoo module ECOSIRE designs and develops to close exactly that gap. At its core is a monthly per-employee attendance calendar — an OWL client-side component backed by hr.attendance and hr.employee — that renders each day colour-coded by presence, absence, partial day, or leave, with worked-hours totals rolled up per week and per month. On top of it sits an advanced HR dashboard built from computed models: aggregate models.Model records with @api.depends compute fields and read_group queries that surface headcount present, total and average hours, late arrivals, early departures, and overtime, filterable by department, job position, work location, and date range. Where it helps, we also expose the metrics through Odoo's native pivot and graph views and ship printable QWeb monthly summary reports for payroll and audit.
Technically, the module is a clean, upgrade-safe addon with its own __manifest__.py, dedicated models and stored/computed fields, ir.model.access.csv plus record rules so an employee sees only their own calendar while HR managers see the whole company, XML and OWL views for the calendar widget, and optional ir.cron jobs or automated actions to pre-aggregate heavy metrics overnight for large databases. It reads existing attendance data with no destructive migration, respects multi-company boundaries, and integrates with hr.leave so approved time off shows correctly on the calendar. It can also be queried through Odoo's XML-RPC/JSON-RPC API if you want to feed the summaries into an external BI tool. We target Odoo 17.0, 18.0, and 19.0 and adapt to whether you run Community or Enterprise (for example, gracefully handling the presence of the Enterprise Planning and advanced HR apps).
Because this is made to order, delivery follows a scoping-first path: a short call to confirm which metrics, filters, and reports you need, a fixed quote against that scope, then development, UAT on a staging copy of your database, and installation on production with a support window afterward. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company consolidation, deep localization of overtime or shift rules, and larger historical-data aggregation increase the quoted scope.
Needs a single dashboard showing who is present, total and average hours, and late or overtime trends by department, without exporting `hr.attendance` to spreadsheets every pay cycle.
Wants reliable monthly worked-hours summaries per employee, printable for the payroll cut-off and reconcilable against leave, so overtime and absences are captured before running payroll.
Wants a monthly calendar view of their own team's attendance to spot chronic lateness or absence patterns early, with visibility limited to their department by record rules.
Runs Odoo across multiple companies and needs consolidated attendance analytics that respect company boundaries and can feed an external BI tool via the API.
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| Attendance calendar view | Purpose-built OWL monthly calendar, colour-coded by presence and leave | Possible but you design and maintain the widget yourself | Often a fixed calendar with limited configurability | |
| Advanced HR dashboard | Aggregate models with KPIs, filters, and pivot/graph, built to your metrics | Fully bespoke but full build cost and timeline on you | Generic dashboard, may not match your KPIs or rules | |
| Fit to your rules | Thresholds, overtime, and schedules tailored during scoping | Fully tailored, entirely your specification and effort | Limited to the vendor's configuration options | |
| Security and access control | Record rules scoped to employee, team, and HR manager as you define | Whatever you build and test yourself | Depends on the module; often coarse-grained | |
| Odoo version coverage | Built and tested for 17.0, 18.0, 19.0, Community or Enterprise | Whatever you target and maintain | Varies; may lag new releases or charge per version | |
| Support and ownership | Support window, docs, training, and git repo handover included | You own all maintenance and documentation | Vendor support terms vary; source may be obfuscated | |
| Cost and predictability | Indicative from $249, fixed quote after scoping | Open-ended developer time and project risk | Low list price but rigid and may need customization anyway | |
| Delivery model | Scoping, UAT on staging, rollback plan, production install | Depends on your internal process and capacity | Self-install; you handle testing and rollout |
This is a build-to-order module, so we start with a short scoping call, then build against a confirmed scope. Typical delivery is 2–4 weeks from confirmed scope, depending on how many metrics, custom rules, and reports you need and the size of your historical attendance data.
No. ECOSIRE designs, builds, installs, and supports this module specifically for your database. It is a productized service, not an off-the-shelf instant download, which is why it fits your working schedules, thresholds, and security model exactly.
Pricing starts from $249 as an indicative, single-company base scope. After a short scoping call we send a fixed quote for your confirmed requirements. Drivers such as multi-company consolidation, deep overtime or shift-rule localization, and large historical-data aggregation adjust the quote.
We build and test for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. We adapt to your edition — for example handling how Enterprise HR and Planning apps are present — and confirm your exact version during scoping.
Every engagement includes a post-go-live support window for defect fixes and questions. Because we hand over the git repository and full documentation, your team can maintain it, and we offer ongoing support or version-upgrade work (for example moving from 17.0 to 19.0) as a separate agreement.
No. The module reads existing `hr.attendance` records and adds its own aggregate models and views without destructive migration. We validate everything on a staging copy of your database during UAT and keep a documented rollback plan before touching production.
Only if you want them to. Access is enforced with `ir.model.access.csv` and record rules: by default an employee sees only their own calendar, team leads see their department, and HR managers see the whole company. We tailor the access groups during scoping.
A made-to-order Odoo module delivering an employee attendance calendar, monthly summaries, and an advanced HR analytics dashboard. ECOSIRE scopes, builds, installs, and supports it on your Odoo 17, 18, or 19 database.