商品詳細は英語で表示されます。翻訳は近日公開予定です。
簡単な事実
- 価格
- $249.00 USD
- Odoo のバージョン
- 17, 18, 19
- セットアップ時間
- 20160分
- ライセンス
- ワンタイム永続
- 言語
- 11 言語
一回購入
Odoo OEE & Work Center Performance Monitor
Build-to-order Odoo module that auto-calculates OEE (Availability × Performance × Quality) per work center with live downtime tracking and loss analysis.
$249.00USD
今すぐのお支払いはありません。これはチームへの見積もり依頼を送信します。価格と次のステップをメールでご案内します。
主な機能
Automatic OEE calculation (Availability × Performance × Quality) per work center and per machine, stored as @api.depends compute fields so numbers refresh the moment a work order or downtime record changes
Six-big-losses categorization — breakdown, setup/adjustment, idling/micro-stops, reduced speed, defects/rework, and startup/yield — mapped onto extended mrp.workcenter.productivity.loss records
Structured downtime and blocked-reason capture from the work-order screen, with a reason tree operators pick from and mandatory notes for major stops
Shift- and calendar-aware availability that reads each work center's resource.calendar, subtracts only planned stops, and never counts scheduled breaks as loss
Configurable OEE targets per work center (and world-class benchmark lines) with automated alerts when rolling OEE falls below target
Pareto charts of downtime causes and loss minutes so teams attack the vital few reasons driving the most lost time
Trend dashboards by line, product, operator, and shift built with OWL and Odoo graph/pivot views for period-over-period comparison
Ideal-cycle-time master data per operation/product used to compute the Performance factor accurately instead of assuming nameplate speed
Quality factor sourced from scrap and rework quantities (and Odoo Quality checks on Enterprise) so defects and startup losses reduce OEE honestly
Automated actions via base.automation to escalate repeat breakdowns, notify the responsible engineer, or open a maintenance/activity when a threshold is breached
QWeb PDF reports for daily shift OEE and monthly management review, ready to print or email from the record
Full XML-RPC / JSON-RPC read access to OEE and loss data for Power BI, Grafana, or a plant-floor MES, plus scheduled ir.cron rollups for fast dashboards
Role-based security via ir.model.access.csv and record rules — operators log downtime, supervisors review, only managers edit targets and reason master data
Multi-company and multi-plant aware, respecting Odoo company rules and per-work-center configuration
この製品について
Odoo's core Manufacturing app tells you what was produced — it doesn't tell you how efficiently your equipment ran. The OEE & Work Center Performance Monitor is a build-to-order module that ECOSIRE designs, develops, installs, and supports specifically for your plant. It computes Overall Equipment Effectiveness — the classic Availability × Performance × Quality formula — automatically for every work center and machine, straight from your existing mrp.workorder, mrp.workcenter, and mrp.workcenter.productivity records, so you get a true, defensible efficiency number instead of a spreadsheet guess.
Odoo OEE & Work Center Performance Monitorを選ぶ理由
Automatic OEE calculation (Availability × Performance × Quality) per work center and per machine, stored as @api.depends compute fields so numbers refresh the moment a work order or downtime record changes
Six-big-losses categorization — breakdown, setup/adjustment, idling/micro-stops, reduced speed, defects/rework, and startup/yield — mapped onto extended mrp.workcenter.productivity.loss records
Structured downtime and blocked-reason capture from the work-order screen, with a reason tree operators pick from and mandatory notes for major stops
Shift- and calendar-aware availability that reads each work center's resource.calendar, subtracts only planned stops, and never counts scheduled breaks as loss
Configurable OEE targets per work center (and world-class benchmark lines) with automated alerts when rolling OEE falls below target
Pareto charts of downtime causes and loss minutes so teams attack the vital few reasons driving the most lost time
Under the hood this is a proper Odoo addon: a clean __manifest__.py declaring dependencies on mrp (plus quality where Enterprise is available), new models.Model classes such as ecosire.oee.line and ecosire.downtime.reason with stored, indexed compute fields (availability, performance, quality, oee — each defined with @api.depends so Odoo recomputes them the instant an underlying value changes). Loss reasons extend the standard mrp.workcenter.productivity.loss records and map cleanly onto the six big losses. Access is locked down with ir.model.access.csv and record rules so operators can log downtime but only managers can edit OEE targets or reason master data. Reporting is delivered through list, pivot, graph, and OWL dashboard views, with QWeb PDF reports for shift and management review, and everything is reachable over XML-RPC / JSON-RPC for BI tools or a plant-floor MES.
Because it's built for you, availability is genuinely accurate: the module reads each work center's working calendar and shift pattern, subtracts only planned stops, and treats unplanned stops as real downtime — no more counting scheduled breaks as losses. Automated actions (Odoo base.automation) can flag a work center the moment its rolling OEE drops below your configured target, escalate a recurring breakdown, or push a discrepancy to the responsible engineer. The result is a live, drill-down picture of where your throughput is actually leaking — by line, product, shift, and operator — and a categorized loss backlog your team can attack with real Pareto data.
Delivered for Odoo 17, 18, and 19 (Community and Enterprise), tuned to your work-center layout and loss taxonomy, with source code, documentation, and a training + support window included. This is a bespoke engagement with a typical 2–4 week build-and-install lead time — not an instant download.
得られるもの
- Complete, installable Odoo module (source code) packaged for your Odoo 17, 18, or 19 database — Community or Enterprise — with clean __manifest__.py, models, security, views, and QWeb reports
- Configured loss taxonomy and OEE targets: your six-big-losses reason tree, ideal cycle times, and per-work-center target lines set up against your real routings
- OWL dashboards and pivot/graph reports plus PDF shift and management OEE reports, tailored to your line/product/operator structure
- Data-integration hooks: XML-RPC/JSON-RPC access documented, optional scheduled rollup jobs, and a mapping spec if you plan to feed an external BI/MES tool
- Technical and user documentation — architecture notes, model/field reference, security matrix, and a step-by-step operator guide for logging downtime
- Live training session(s) for plant managers, supervisors, and operators, recorded for onboarding future staff
- Deployment to your staging then production environment with an upgrade/migration path and a rollback plan
- A defined post-go-live support and warranty window covering bug fixes and minor adjustments after acceptance
これは誰のためのものですか
Plant / Production Manager
Owns line efficiency and throughput targets. Needs one trustworthy OEE number per work center and shift — sourced from Odoo, not a manual spreadsheet — with drill-down into the losses dragging output down and alerts when a line slips below target.
Production / Manufacturing Engineer
Runs continuous-improvement and Kaizen. Wants clean six-big-losses data and Pareto charts to prioritize the vital-few downtime causes, plus accurate ideal-cycle-time and speed-loss figures to justify capex and process changes.
Maintenance / Reliability Lead
Cares about breakdown and setup losses. Uses categorized downtime capture and automated escalations to spot recurring machine failures, tie them to maintenance activities, and prove the reliability impact on availability.
Operations Director / COO
Tracks efficiency across multiple lines or plants. Needs period-over-period OEE trends and management PDF reports, and wants the metric feeding the wider BI stack over XML-RPC/JSON-RPC for board-level reporting.
インストールの概要
ECOSIREからダウンロード
ecosire.com でライセンスを購入し、アカウント ダッシュボードから Odoo OEE & Work Center Performance Monitor モジュールの ZIP をダウンロードします。
Odoo にアップロードする
ZIP をサーバー上の Odoo カスタム アドオン フォルダーに抽出します (または、[アプリ] > [Odoo.sh / runbot のファイルからインストール] を介してアップロードします)。
モジュールをインストールする
開発者モードをアクティブにし、アプリを開き、「アプリリストの更新」をクリックして、「Odoo OEE & Work Center Performance Monitor」を検索し、「インストール」を押します。
設定を構成する
新しいメニューを開き、ECOSIRE ライセンス キーを貼り付け、外部認証情報 (Shopify、Amazon、Stripe など) を接続して保存します。
検証して公開する
組み込みの接続テストを実行し、最初の 10 レコードを同期し、定期的な cron をスケジュールします。何か問題が発生した場合はサポートにお問い合わせください。
Odoo OEE & Work Center Performance Monitor の比較方法
| 基準 | エコシエール | カスタムビルド | 競合他社 | オドゥー ネイティブ |
|---|---|---|---|---|
| True OEE = Availability × Performance × Quality, auto-calculated | 付属 | 部分的なサポート | 部分的なサポート | |
| Fits your exact work-center layout, shifts & loss taxonomy | 付属 | 付属 | 含まれていない | |
| Six-big-losses categorization with Pareto analysis | 付属 | 部分的なサポート | 部分的なサポート | |
| Shift/calendar-aware availability (planned vs unplanned stops) | 付属 | 部分的なサポート | 含まれていない | |
| Configurable OEE targets with automated below-target alerts | 付属 | 部分的なサポート | 含まれていない | |
| Delivered, installed & supported for Odoo 17/18/19 by the builder | 付属 | 部分的なサポート | 含まれていない | |
| XML-RPC/JSON-RPC feed to Power BI / MES with scheduled rollups | 付属 | 部分的なサポート | 部分的なサポート | |
| Role-based security (operators log, managers set targets) | 付属 | 部分的なサポート | 部分的なサポート | |
| Full source code ownership & migration path across versions | 付属 | 付属 | 含まれていない |
Odoo OEE & Work Center Performance Monitor に関するよくある質問
How long until the module is delivered and installed?
This is a build-to-order engagement, not an instant download. Typical lead time is 2–4 weeks from a confirmed scope: we begin with a short discovery on your work-center layout, shift calendars, routings, and loss taxonomy, then build against your Odoo version, deliver to staging for your sign-off, and deploy to production. Timeline scales with the number of lines and any external BI/MES integration; we confirm dates in writing before starting.
How are support and updates handled after go-live?
Every engagement includes a defined post-go-live support and warranty window covering bug fixes and minor adjustments after acceptance. You receive the full module source code, so nothing is locked. When you upgrade Odoo (for example 18 to 19) we provide a migration path, and ongoing support or an annual maintenance retainer for enhancements and new-version compatibility is available on request.
Does this work with Odoo Community, or only Enterprise?
Both. The module depends on the standard mrp (Manufacturing) app, which exists in Community and Enterprise, and is delivered for Odoo 17, 18, and 19. On Enterprise we can additionally source the Quality factor from Odoo Quality checks and integrate with Maintenance; on Community we derive quality from scrap/rework quantities. We tailor the build to your exact edition and version.
Where does the OEE data actually come from — do operators have to enter it twice?
No double entry. The module reads your existing manufacturing transactions: work orders (mrp.workorder), work-center productivity/time logs (mrp.workcenter.productivity), scrap, and calendars. Operators only add value where Odoo doesn't already know something — for example picking a structured downtime reason when a stop occurs. Availability, performance, and quality are then computed automatically as @api.depends fields.
Can we feed the OEE numbers into Power BI or another external system?
Yes. All OEE and loss models are exposed over Odoo's XML-RPC and JSON-RPC APIs, and we can add scheduled ir.cron rollup tables so dashboards stay fast. We document the field mappings and, if needed, help wire the feed into Power BI, Grafana, or a plant-floor MES as part of the deliverables.
How is access controlled so operators can't change targets or fudge numbers?
Security is enforced with ir.model.access.csv and record rules. Operators can log downtime and reasons but cannot edit OEE targets, ideal cycle times, or loss master data — those are restricted to supervisor/manager groups. This keeps the metric auditable and consistent across shifts and plants.
関連モジュール
見積もりを依頼
Odoo OEE & Work Center Performance Monitor
Build-to-order Odoo module that auto-calculates OEE (Availability × Performance × Quality) per work center with live downtime tracking and loss analysis.
- Automatic OEE calculation (Availability × Performance × Quality) per work center and per machine, stored as @api.depends compute fields so numbers refresh the moment a work order or downtime record changes
- Six-big-losses categorization — breakdown, setup/adjustment, idling/micro-stops, reduced speed, defects/rework, and startup/yield — mapped onto extended mrp.workcenter.productivity.loss records
- Structured downtime and blocked-reason capture from the work-order screen, with a reason tree operators pick from and mandatory notes for major stops
- Shift- and calendar-aware availability that reads each work center's resource.calendar, subtracts only planned stops, and never counts scheduled breaks as loss