يتم عرض تفاصيل المنتج باللغة الإنجليزية. الترجمات قريبا.
حقائق سريعة
- السعر
- $799.00 USD
- إصدارات أودو
- 17, 18, 19
- وقت الإعداد
- 20 دقيقة
- الترخيص
- مرة واحدة دائمًا
- اللغات
- 11 لغات
شراء لمرة واحدة
Predictive Maintenance (IoT Sensor-Driven)
Condition-based Odoo maintenance that auto-triggers work orders from sensor thresholds — vibration, temperature, runtime. Built, installed & supported by ECOSIRE.
$799.00USD
لا حاجة للدفع الآن. يؤدي هذا إلى إرسال طلب عرض سعر إلى فريقنا — وسنتواصل معك عبر البريد الإلكتروني بالأسعار والخطوات التالية.
الميزات الرئيسية
Sensor-threshold rule engine (`maintenance.threshold.rule`) that auto-creates a `maintenance.request` the moment a reading breaches a configured limit — vibration mm/s, bearing temperature C, motor current A, pressure bar, or any custom meter
Meter-reading ingestion model (`maintenance.meter`) capturing runtime hours, cycle counts, temperature, and vibration per equipment, with timestamp and source, ingested via XML-RPC/JSON-RPC, MQTT bridge, IoT Box, or scheduled CSV/API poll
Condition-based scheduling that fires on a live sensor state, running alongside Odoo's native time-based preventive schedules so a machine can be serviced on whichever trigger comes first
Multi-reading debounce and hysteresis: rules can require N consecutive breaches or a rolling average (e.g. temp > 85 C for 3 readings) to suppress false alarms from a single noisy spike
Equipment health scoring: a `@api.depends`-computed score per `maintenance.equipment` derived from open breaches, meter trends, and overdue services, surfaced as a color-coded kanban and sortable list
Anomaly detection via rolling-window baselines — flags readings that deviate from an equipment's own recent norm even when no absolute threshold is crossed
Tiered escalation using Odoo automated actions and activities: warning threshold pings the assigned technician; critical threshold escalates to the maintenance manager and can auto-raise request priority to Urgent
Health-scoring dashboard (OWL + graph/pivot views) showing fleet status, top risk assets, breach history, and meter trend charts, drillable straight into the equipment form
`ir.cron` polling job that pulls readings from external gateways on a configurable interval and re-evaluates all active rules, so ingestion never depends on the sensor pushing perfectly
Automatic work-order routing: generated requests inherit the equipment's maintenance team, category, and default technician, and (with `mrp`) can block or flag the linked work center
Role-scoped security via `ir.model.access.csv` and record rules — operators log/read meters, planners manage rules, only managers close critical escalations; multi-plant record rules keep sites isolated
QWeb PDF reports for maintenance history, breach log, and MTBF/MTTR summaries per equipment or team, plus exportable pivots for reliability review meetings
Meter-based service intervals (e.g. every 500 runtime hours or 10,000 cycles) that reset on request completion — true usage-based maintenance, not calendar-only
Full audit trail on every equipment record: readings, rule breaches, generated requests, and escalations logged in the native Odoo chatter for traceability
عن هذا المنتج
Reactive maintenance is expensive. You wait for a bearing to scream, a motor to overheat, or a spindle to fail — then you scramble a crew, eat the unplanned downtime, and explain the scrapped batch. Odoo's core Maintenance app gives you time-based preventive schedules and manual requests, but it has no concept of a live sensor reading. It can't know that pump P-114's vibration just crossed 7.1 mm/s, or that conveyor motor M-08 has logged 4,000 runtime hours since its last service. That gap is exactly what this module closes.
لماذا تختار Predictive Maintenance (IoT Sensor-Driven)
Sensor-threshold rule engine (`maintenance.threshold.rule`) that auto-creates a `maintenance.request` the moment a reading breaches a configured limit — vibration mm/s, bearing temperature C, motor current A, pressure bar, or any custom meter
Meter-reading ingestion model (`maintenance.meter`) capturing runtime hours, cycle counts, temperature, and vibration per equipment, with timestamp and source, ingested via XML-RPC/JSON-RPC, MQTT bridge, IoT Box, or scheduled CSV/API poll
Condition-based scheduling that fires on a live sensor state, running alongside Odoo's native time-based preventive schedules so a machine can be serviced on whichever trigger comes first
Multi-reading debounce and hysteresis: rules can require N consecutive breaches or a rolling average (e.g. temp > 85 C for 3 readings) to suppress false alarms from a single noisy spike
Equipment health scoring: a `@api.depends`-computed score per `maintenance.equipment` derived from open breaches, meter trends, and overdue services, surfaced as a color-coded kanban and sortable list
Anomaly detection via rolling-window baselines — flags readings that deviate from an equipment's own recent norm even when no absolute threshold is crossed
Predictive Maintenance (IoT Sensor-Driven) is a net-new Odoo module that ECOSIRE designs, builds, installs, and supports for you. It turns your instrumented machinery into a self-monitoring fleet: meter readings stream in (via XML-RPC/JSON-RPC from your PLC gateway, MQTT bridge, or a scheduled CSV/API poll), threshold rules evaluate them continuously, and when a condition trips, Odoo automatically creates a maintenance.request on the right equipment, assigned to the right team, at the right severity — no human watching a dashboard required.
Because this is real Odoo, everything lives inside your ERP where the rest of the business already works. The module extends maintenance.equipment with a new maintenance.meter model for readings and a maintenance.threshold.rule model for the logic. Rules are stored records — not hard-coded — so your maintenance planner can add "temperature > 85 C for 3 consecutive readings" without a developer. Equipment health is a @api.depends-driven computed score you can sort, filter, group, and drop onto a kanban or dashboard. Alerts escalate through Odoo's native activity and messaging system (the chatter you already use), and every reading, breach, and generated work order is auditable.
We ground the build in proper Odoo engineering, not a bolt-on script: a clean __manifest__.py declaring dependencies on maintenance (and optionally mrp for manufacturing plants); ORM models with typed fields; compute methods decorated with @api.depends; access control via ir.model.access.csv plus record rules so an operator sees only their plant's equipment; XML views (list, form, kanban, graph, pivot) and OWL components for the live health board; QWeb reports for maintenance history and MTBF summaries; ir.cron jobs and Odoo automated actions to poll meters and fire escalations; and an XML-RPC/JSON-RPC ingestion endpoint so any sensor gateway can push data. It runs on Odoo 17, 18, and 19, and works on both Community and Enterprise (Enterprise's IoT Box, if you have it, is one supported input path — but nothing here requires it).
This is build-to-order: after purchase, an ECOSIRE Odoo engineer scopes your equipment, sensor types, and rules with you, then delivers a fully configured module tuned to your plant — typically in 2 to 4 weeks. It is not an instant download from apps.odoo.com. You get the source, the config, documentation, training, and a support window (details below).
ما تحصل عليه
- Complete, installable Odoo module source (`__manifest__.py`, Python models, XML/OWL views, `ir.model.access.csv`, record rules, QWeb reports, cron and automated-action data) — yours to keep, version-controlled
- Configured threshold rules, meter definitions, and health-scoring weights tuned to your actual equipment list and sensor types, loaded into your database
- Sensor ingestion setup: a working XML-RPC/JSON-RPC (or MQTT/CSV-poll) pathway wired to your PLC gateway or IoT source, with a documented payload format
- Deployment on your environment — Odoo Online (where compatible), Odoo.sh, or self-hosted / ECOSIRE-managed — with the module installed, tested, and verified against sample readings
- Documentation set: admin/config guide, rule-authoring guide for your planners, ingestion API reference, and an operations runbook
- Live training session(s) for maintenance planners, technicians, and admins, plus a recording
- A defined post-go-live support window with bug fixes and Odoo 17/18/19 compatibility maintenance (see FAQ)
- Source-code handover to your Git repository (or ours, your choice) so you own the IP and can extend it later
لمن هذا
Maintenance / Reliability Manager
Owns uptime and the maintenance budget at an instrumented plant. Wants to shift from reactive firefighting to predictive, condition-based servicing — and prove MTBF/MTTR improvement to leadership — without ripping out Odoo for a standalone CMMS.
Plant / Operations Engineer
Runs the floor and already has sensors or a PLC/SCADA gateway producing vibration, temperature, and runtime data that currently dies in a historian nobody reads. Needs that data to automatically create actionable work orders in the system the team already lives in.
Odoo Administrator / IT Lead
Responsible for the Odoo deployment across 17/18/19 and Community/Enterprise. Wants a clean, well-secured, ORM-native module with proper access rules and a documented ingestion API — not a fragile external script hitting the database.
نظرة عامة على التثبيت
تحميل من ECOSIRE
قم بشراء الترخيص من موقع ecosire.com وقم بتنزيل وحدة Predictive Maintenance (IoT Sensor-Driven) ZIP من لوحة تحكم حسابك.
تحميل إلى أودو
قم باستخراج ملف ZIP إلى مجلد إضافات Odoo المخصصة على الخادم (أو تحميله عبر التطبيقات > التثبيت من ملف على Odoo.sh / runbot).
قم بتثبيت الوحدة
قم بتنشيط وضع المطور، وافتح التطبيقات، وانقر فوق تحديث قائمة التطبيقات، وابحث عن Predictive Maintenance (IoT Sensor-Driven)، ثم اضغط على تثبيت.
تكوين الإعدادات
افتح القائمة الجديدة، والصق مفتاح ترخيص ECOSIRE الخاص بك، وقم بتوصيل أي بيانات اعتماد خارجية (Shopify، وAmazon، وStripe، وما إلى ذلك)، ثم احفظها.
التحقق والبدء في البث المباشر
قم بتشغيل اختبار الاتصال المدمج، وقم بمزامنة أول 10 سجلات لديك، وقم بجدولة عملية cron المتكررة. اتصل بالدعم إذا فشل أي شيء.
كيف يقارن Predictive Maintenance (IoT Sensor-Driven).
| المعيار | ECOSIRE | بناء مخصص | منافس | أودو الأصلي |
|---|---|---|---|---|
| Auto-creates work orders from live sensor thresholds | متضمنة | Possible but you design and maintain the rule engine yourself | Rarely — most off-the-shelf maintenance apps are time/meter-based, not true condition-based | |
| Sensor ingestion (XML-RPC/JSON-RPC/MQTT/CSV poll) | متضمنة | You build every connector from scratch | Partial — often a single fixed input format | |
| Condition-based + time-based scheduling together | متضمنة | Depends entirely on your build scope | دعم جزئي | |
| Equipment health scoring & anomaly detection | متضمنة | Only if you spec and build the compute logic | غير متضمنة | |
| Tiered escalation via automated actions & activities | متضمنة | You wire the escalation logic yourself | دعم جزئي | |
| Built, installed & supported for you (2–4 wk delivery) | متضمنة | You own all delivery, timeline, and risk | غير متضمنة | |
| Runs on Odoo 17/18/19, Community & Enterprise | متضمنة | Your responsibility to keep compatible | Varies by vendor and version | |
| You own the source code & security (record rules, ACLs) | متضمنة | متضمنة | Usually closed / vendor-locked |
الأسئلة المتداولة حول Predictive Maintenance (IoT Sensor-Driven)
How long until it's live, and is this an instant download?
This is build-to-order, not an instant apps.odoo.com download. After purchase, an ECOSIRE Odoo engineer runs a short scoping call to map your equipment, sensor types, and the rules you need. We then build, configure, and install the module on your environment. Typical delivery is 2 to 4 weeks depending on how many equipment types, sensor sources, and escalation paths are in scope — we confirm a firm timeline during scoping.
What support and updates do I get after go-live?
Delivery includes a post-go-live support window covering bug fixes and configuration adjustments, plus compatibility maintenance across Odoo 17, 18, and 19 so a version upgrade doesn't break your predictive maintenance. You keep the source code, so your own team can extend it too. Ongoing enhancements, new rule types, or additional sensor integrations after the window are available on a support-retainer or fixed-scope basis.
Does this work with Odoo Community, or do I need Enterprise?
It works on both. The module only depends on the core `maintenance` app (and optionally `mrp`), which exist in Community. If you run Enterprise and have an IoT Box, that's one supported ingestion path — but nothing here requires Enterprise or the IoT Box. Readings can arrive via XML-RPC/JSON-RPC, an MQTT bridge, or a scheduled CSV/API poll from any gateway.
How do sensor readings actually get into Odoo?
We wire your data source to a documented ingestion path. Most plants push readings from a PLC/SCADA gateway or edge device into the `maintenance.meter` model over Odoo's XML-RPC or JSON-RPC API. For push-based setups we support an MQTT bridge; for systems that can only export files, an `ir.cron` job polls a CSV or REST endpoint on an interval and re-evaluates all rules. We confirm the best fit for your infrastructure during scoping.
How is this different from Odoo's built-in Maintenance preventive schedules?
Odoo core does time-based preventive maintenance (service every 90 days) and manual requests, but it has no awareness of live sensor data. This module adds condition-based triggering: rules evaluate real readings — vibration, temperature, runtime hours, cycles — and auto-create work orders when a limit is breached, with debounce to avoid false alarms, health scoring, and tiered escalation. It runs alongside your existing time-based schedules, not instead of them.
Can I edit the threshold rules myself without a developer?
Yes. Rules are stored Odoo records (`maintenance.threshold.rule`), not hard-coded logic. Once we hand over, a maintenance planner with the right access can add or adjust thresholds, consecutive-breach counts, target equipment, severity, and escalation routing directly in the Odoo UI. Record rules and `ir.model.access.csv` control who can change what, and every change is captured in the chatter audit trail.
الوحدات ذات الصلة
طلب عرض سعر
Predictive Maintenance (IoT Sensor-Driven)
Condition-based Odoo maintenance that auto-triggers work orders from sensor thresholds — vibration, temperature, runtime. Built, installed & supported by ECOSIRE.
- Sensor-threshold rule engine (`maintenance.threshold.rule`) that auto-creates a `maintenance.request` the moment a reading breaches a configured limit — vibration mm/s, bearing temperature C, motor current A, pressure bar, or any custom meter
- Meter-reading ingestion model (`maintenance.meter`) capturing runtime hours, cycle counts, temperature, and vibration per equipment, with timestamp and source, ingested via XML-RPC/JSON-RPC, MQTT bridge, IoT Box, or scheduled CSV/API poll
- Condition-based scheduling that fires on a live sensor state, running alongside Odoo's native time-based preventive schedules so a machine can be serviced on whichever trigger comes first
- Multi-reading debounce and hysteresis: rules can require N consecutive breaches or a rolling average (e.g. temp > 85 C for 3 readings) to suppress false alarms from a single noisy spike