Odoo
Implementation
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Inventory (stock) • Discuss (mail) |
| Lines of code | 15 |
| Technical Name |
mrp_default_operation |
| License | OPL-1 |
| Website | https://lucidbrainz.com/?i=1 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Manufacturing (mrp)
• Inventory (stock) • Discuss (mail) |
| Lines of code | 15 |
| Technical Name |
mrp_default_operation |
| License | OPL-1 |
| Website | https://lucidbrainz.com/?i=1 |
LB MRP BOM Default Operations for Odoo 18
Define Default Operations on BOM | Auto Work Orders in Manufacturing | Work Center Linking | Operation Templates
Overview
LB MRP BOM Default Operations by LucidBrainz is a smart manufacturing enhancement module for Odoo 18 that allows you to define default work center operations directly on the Bill of Materials (BOM). Instead of manually adding operations every time a Manufacturing Order is created, this module lets you pre-configure operations — with work center, duration, and computation method — at the BOM level itself. When a Manufacturing Order is created using that BOM, the defined operations automatically populate in the Work Orders tab, saving significant time and eliminating human error. Fully compatible with Odoo's standard Manufacturing module, this solution is ideal for production teams that follow repetitive manufacturing processes and want consistent, standardized operation templates across all their production orders!
Key Features
- Default Operations on Bill of Materials: Define one or more default operations directly on the BOM form under the dedicated Operations tab. Each operation stores Work Center, Duration Computation method, Default Duration (in minutes), Employee Capacity, and Worksheet details. Operations defined here serve as templates that auto-apply to every Manufacturing Order created using that BOM — no manual entry needed.
- Work Center Linking: Each operation on the BOM is directly linked to a specific Work Center (e.g., Assembly 1, Drill 1, Assembly 2). This ensures the right work center is always assigned to the right operation automatically. Work Center data including Code, Tag, Capacity, Time Efficiency, and OEE Target is maintained separately and linked cleanly via the operation.
- Flexible Duration Computation: For each BOM operation, choose between two duration computation modes — Compute based on tracked time (time tracking driven) or Set duration manually (fixed minutes). Default duration is set in minutes directly on the operation. Employee Capacity can be defined per operation to support workforce planning in production scheduling.
- Copy Existing Operations: Use the Copy Existing Operations shortcut on the BOM Operations tab to quickly replicate operations from another BOM. This is especially useful when multiple products share similar manufacturing steps — define once, copy everywhere. Saves configuration time and maintains consistency across product BOMs.
- Operations List View with BOM Reference: Navigate to Configuration → Operations to get a centralized list of all operations across all BOMs. Each row shows Operation Name, linked Bill of Material, Work Center, Duration Computation, and Duration (minutes). This makes it easy to audit and review all manufacturing operations from a single screen without opening each BOM individually.
- Worksheet Support per Operation: Each operation supports a Worksheet configuration — choose between PDF, Google Slide, or Text formats. Attach step-by-step work instructions, quality checklists, or assembly guides directly to the operation. Workers on the shop floor can access these instructions from the Work Order screen during production without leaving Odoo.
- Auto Work Orders in Manufacturing Orders: When a Manufacturing Order is created using a BOM that has default operations defined, those operations automatically appear in the Work Orders tab of the Manufacturing Order. This eliminates repetitive manual data entry on every production run and ensures every Manufacturing Order follows the standardized process defined on the BOM.
- BOM-level Operation Storage: Operations are stored at the BOM level via a Many2many relationship with mrp.routing.workcenter, with a reverse bom_id link on the operation itself. This ensures full traceability — every operation knows which BOM it belongs to, and every BOM knows which operations it carries. The copy=True flag ensures operations are preserved when a BOM is duplicated.
Odoo 18 Module Screenshots
Our Services
Odoo
Customization
Odoo
Migration
Support &
Maintenance
📞 Contact Us
WhatsApp:
Email:
Website: |
🌐 Follow Us📘 Facebook 📸 Instagram 💼 LinkedIn 🎥 YouTube |
© 2025 LucidBrainz InfoTech | All Rights Reserved | License: OPL-1
Odoo 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