| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Maintenance (maintenance)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 330 |
| Technical Name |
mjb_remind_preventive_maintenance |
| License | OPL-1 |
| Website | https://www.majorbird.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Maintenance (maintenance)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 330 |
| Technical Name |
mjb_remind_preventive_maintenance |
| License | OPL-1 |
| Website | https://www.majorbird.com |
Preventive Maintenance Reminder
Automatically reminds your maintenance team 30 days before equipment is due for preventive maintenance — so nothing falls through the cracks and production keeps running.
by Majorbird — Odoo Silver Partner
The Problem
Preventive maintenance gets skipped when the team is busy. Equipment sits past its scheduled service date because no one received a reminder — and the next thing you know, a critical machine breaks down mid-production. Emergency repairs cost 5–10x more than scheduled maintenance, and unplanned stoppages ripple through the entire production schedule. Odoo records the next action date on every equipment card, but does nothing to alert anyone when that date is approaching.
How It Works
| Parameter | Value |
|---|---|
| Model | maintenance.equipment |
| Condition | x_next_maintenance_date within 30 days |
| Recipient | Maintenance team / responsible technician |
| Frequency | Daily cron — fully automatic |
Key Features
30-Day Advance Warning
Reminders fire 30 days before the scheduled x_next_maintenance_date, giving the team enough lead time to plan the work, order parts, and schedule downtime without disruption.
Sent to Maintenance Team
The reminder targets the responsible technician assigned to the equipment, or the full maintenance team if no specific person is set — ensuring the right people are always notified.
Daily Cron — No Manual Work
A scheduled cron job runs every day and checks all equipment automatically. No one needs to remember to trigger it — the system handles everything in the background.
Prevent Unexpected Breakdowns
Proactive reminders shift maintenance from reactive to preventive — reducing emergency repair costs, unplanned stoppages, and the operational chaos that follows a sudden equipment failure.
Configuration
Install the module
Install Preventive Maintenance Reminder from the Odoo Apps menu. No additional configuration is required at this stage — the cron job is registered automatically on install.
Ensure equipment has a Next Action Date
Go to Maintenance > Equipment and verify that each piece of equipment has the Next Action Date field populated. Equipment without a date will not receive reminders. Assign a responsible technician if needed.
Reminders fire automatically every day
The daily cron job checks all active equipment and sends reminders for those with a next action date within the next 30 days. No further action is required — the system runs continuously from the moment of installation.
Scope & Limitations
This is a focused satellite module. It does one thing well.
- ✕ Does NOT reschedule maintenance — it only sends reminders about existing scheduled dates.
-
✕
Does NOT affect equipment without a
x_next_maintenance_dateset — those records are ignored. - ✕ Does NOT require the Maintenance app's paid enterprise features — works with the standard community Maintenance module.
maintenance.equipment no longer has a
native next_action_date field. This module adds a custom
x_next_maintenance_date Date field to maintenance.equipment via model
inheritance (v19.0.1.0.1). Set this date on each piece of equipment to activate reminders.
About Majorbird
Odoo Silver Partner — Manufacturing, Inventory & Accounting Automation
Offices in Vietnam, China, Mexico, and the Middle East.
www.majorbird.comOdoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module