Management System - Nonconformity Maintenance Equipment
This module allows the user to relate maintenance equipment to a nonconformity.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Adds an Equipment field to nonconformities so you can link each nonconformity to a piece of maintenance equipment, and lets you group nonconformities by equipment.
This module connects nonconformities with maintenance equipment. On every nonconformity record you now get an extra "Equipment" field where you can pick the machine or asset the issue relates to.
Where it appears: - On the nonconformity form, the Equipment field is shown just before the creation date. - In the nonconformity list, the Equipment column appears right after the partner column. - In the nonconformity search filters, a new "Equipment" grouping option is added after the manager grouping, so you can group and analyse nonconformities by equipment.
What it changes:
- The mgmtsystem.nonconformity model gains a link to maintenance.equipment.
- No automatic checks, computations, default values, emails or scheduled jobs are added; the field is simply available for manual selection.
This is useful when you want to track which equipment is involved in quality or safety issues and review nonconformities per machine.
Depends on
Models and fields (1)
- mgmtsystem.nonconformity · extends an existing modelequipment_id (Equipment)
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/management-system.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0NC Maintenance
- Go to Management System → Nonconformity
- Create new Nonconformity
- Select a Equipment
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.