PLM Lifecycle
by Baris Genc https://gencbaris.com/odoo_plugins/plm_product_lifecycle/index.html$ 38.61
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Manufacturing (mrp) • Inventory (stock) |
| Lines of code | 244 |
| Technical Name |
plm_product_lifecycle |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/plm_product_lifecycle/index.html |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Manufacturing (mrp) • Inventory (stock) |
| Lines of code | 244 |
| Technical Name |
plm_product_lifecycle |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/plm_product_lifecycle/index.html |
| Versions | 17.0 18.0 19.0 |
PLM Lifecycle
Product design, BOM versioning, ECO management, CAD integration
Complete Product Lifecycle Management for managing product design, BOM versioning, engineering change orders (ECO), CAD integration, and compliance tracking from concept to obsolescence.
Key Features
Product Design Management
Centralized design repository with stage-gate process, design reviews, and concept approval workflow.
BOM Versioning
Multi-level BOMs with version control, effectivity dates, and alternate component management.
Engineering Change Orders
Full ECO workflow with change request, impact analysis, approval routing, and implementation tracking.
CAD Integration
CAD file management, 3D model viewer, drawing version control and metadata extraction.
Compliance Tracking
RoHS, REACH and FDA regulatory tracking with material declarations and hazmat management.
Document Management
Technical documents, specifications, test reports and certifications with controlled distribution.
Component Lifecycle
Component sourcing, supplier management, obsolescence tracking and alternative parts.
Release & Genealogy
Design freeze, release approval, as-designed vs as-built tracking and full traceability.
Use Cases
Electronics
Manufacturers with frequent design iterations and short product cycles.
Automotive
Suppliers with strict compliance and PPAP-style change controls.
Medical Devices
FDA-regulated manufacturers needing full design history files.
Machinery
Builders with deep multi-level BOMs and configurable products.
Why Choose This
50% faster ECO cycle
Automated routing, approvals and impact analysis cut change-order turnaround in half.
100% compliance
Built-in RoHS/REACH/FDA tracking keeps regulatory submissions audit-ready.
40% fewer design errors
Versioned BOMs and controlled releases eliminate revision confusion on the shop floor.
Specifications
- Compatible with Odoo 17, 18 and 19 (Community & Enterprise)
- License: OPL-1
- 35+ languages supported
- Author: Baris Genc
- Support: odoo@gencbaris.com
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