See the installed product first
Shown with fictional English demonstration data. These are working product views, not design mockups.
Project, Manufacturing and Field Service timesheets under one roof
Bring project and task timesheets, manufacturing order and work order time, and Field Service job timesheets into one governed operational view. Managers can compare employees, departments, customers, projects, production operations and service work without replacing the native Odoo records that remain the source of truth.
Unified Timesheet Manufacturing Connector
Unify operator time with manufacturing order, work order, operation and work-center context for precise planned-versus-actual analysis.
Built for decisions, not decorative totals
A credible view of where manufacturing time went, why variance occurred and which operations need attention.
Operator productivity
Connect employee/operator activity to the work order and manufacturing order that produced it.
Planned versus actual
Compare expected and realized durations with variance, efficiency and capacity impact.
Work-center intelligence
Report work center, operation, product and production reference in every relevant analytical path.
Loss-aware reporting
Keep productive time and work-center loss context explainable without double counting.
Shared approval controls
Manufacturing time participates in the same validation, lock and anomaly governance as project time.
Native source integrity
MRP records remain authoritative; the reporting model is an idempotent analytical projection.
Observe
Read authoritative Odoo business records.
Reconcile
Synchronize reporting context idempotently.
Explain
Expose traceable KPIs, anomalies and drill-down.
Act
Approve, correct and improve with confidence.
Real operational screens
Premium, multilingual and designed to preserve the context behind every number.
Designed for production Odoo
| Sources | Manufacturing orders, work orders and productivity |
| Dimensions | Operator, operation, work center and product |
| Measures | Planned, actual, variance and efficiency |
| Dependency | Unified Timesheet Core |
Your Odoo data remains yours
The suite is an analytical and workflow layer. Project, task, manufacturing, attendance and leave records remain authoritative in their native Odoo applications. Addon-owned reporting records can be rebuilt, and removing the addon does not require destructive changes to native business data.
Multilingual foundation: translatable interface strings follow the active Odoo language; English is the source language and Turkish translations are included where supplied.
Clear dependencies, governed capabilities
Install only the capabilities you need. Core is the governed foundation; connectors preserve their native domain context; Dashboard turns the combined dataset into the premium management experience.
| Module | Relationship |
|---|---|
| Unified Timesheet Core | Required foundation |
| Unified Timesheet Dashboard | Requires Core + Project + MRP |
| Unified Timesheet Project Connector | Requires Core |
| Unified Timesheet MRP Connector | Requires Core |
| Unified Timesheet Attendance Bridge | Requires Project + MRP |
Expose planned-versus-actual production time from operator to work center.
Move beyond totals. Every score is paired with a formula, a valid denominator, a reporting period and a path back to the Odoo records that produced it.
Find the operation behind every variance.
Separate productive time from classified loss.
Compare schedule attainment and capacity pressure.
Know what each number means before acting on it
The sample values below illustrate the product experience. Your results are calculated from your own authorized Odoo records and selected reporting period.
| Score | Example | Calculation basis |
|---|---|---|
| OPERATION EFFICIENCY | 91.6% | Planned duration / actual duration |
| WORK CENTER USE | 86.2% | Productive time / available work-center capacity |
| SCHEDULE ATTAINMENT | 94.0% | On-plan completed work / scheduled work |
| PRODUCTIVE TIME RATIO | 88.8% | Productive duration / total tracked duration |
| OPERATOR CONTRIBUTION | 17.4% | Operator productive hours / team productive hours |
| DURATION VARIANCE | +26.4 h | Actual duration - planned duration |
| LOSS EXPOSURE | 6.7% | Classified loss duration / tracked duration |
| CYCLE RELIABILITY | 92.3% | Operations inside accepted duration tolerance |
See the signal. Understand the formula. Open the evidence. Take action.
Premium presentation is matched by operational depth: multilingual UI, company-aware security, source traceability, period controls and drill-down are part of the product story.
From installation to management action
This guide explains the complete operating model: what must be configured, which native Odoo record remains authoritative, how the reporting layer is refreshed, how managers should interpret metrics and how common data-quality issues are resolved.
Installation and first configuration
Prepare a controlled, auditable rollout before exposing metrics to management.
- Install Core and verify Manufacturing, Work Orders and employee/operator relationships in native Odoo.
- Confirm that work centers have calendars and cost configuration where capacity or cost analysis is expected.
- Review operation planned durations and manufacturing quantities; planned-versus-actual reporting depends on credible planning data.
- Synchronize a completed and an active work order, then reconcile operator time against native productivity records.
Daily operating workflow
Understand where data originates and how it becomes visible in the suite.
- Operators start and stop work from the native work-order interface.
- The connector reads manufacturing order, work order, operation, work center, employee and productivity duration.
- Active work is shown in Live Workforce only while an authoritative open productivity or compatible timer record exists.
- Completed durations flow into daily audit, weekly grid and planned-versus-actual analysis after synchronization.
Manager review procedure
Use drill-down and comparable periods to turn indicators into defensible decisions.
- Compare planned and actual duration at operation and work-center level before aggregating to the manufacturing order.
- Separate productive duration from work-center loss categories to avoid blaming operators for classified downtime.
- Investigate extreme variance with quantity, routing, setup, waiting and interruption context.
- Use employee metrics as operational signals and combine them with quality and process evidence.
How the principal indicators are calculated
Percentages are meaningful only when their denominator is valid. Always confirm calendar, leave, planning, cost and source completeness before comparing employees or departments.
| Metric | Formula | Interpretation |
|---|---|---|
| Duration Variance | Actual Duration - Planned Duration | Positive values indicate time above plan. |
| Operation Efficiency | Planned Duration / Actual Duration x 100 | Time efficiency when both durations are positive. |
| Work Center Load | Scheduled Work / Available Work Center Capacity x 100 | Planned pressure on the work center. |
| Operator Contribution | Operator Productive Hours / Team Productive Hours x 100 | Share of productive time, not quality by itself. |
Resolve the cause at the authoritative source
Recommended production acceptance checklist
1. Reconcile a sample period against native Odoo totals.
2. Test multi-company access with real non-admin roles.
3. Confirm timezone and calendar behavior around day boundaries.
4. Verify every KPI drill-down reaches its contributing records.
5. Test approved leave, holiday and no-schedule scenarios.
6. Start and stop each supported timer path.
7. Upgrade in a staging database before production.
8. Document who owns data correction and period approval.
Make time, capacity and performance explainable
Purpose-built for organizations that need operational clarity across project delivery, manufacturing and workforce capacity inside Odoo.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Discuss (mail) • Employees (hr) • Inventory (stock) |
| Community Apps Dependencies | Show |
| Lines of code | 1931 |
| Technical Name |
unified_timesheet_mrp |
| License | LGPL-3 |
Please log in to comment on this module