This module adds an option for the user to select an equipment type for an equipment.
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Lets you create a list of equipment types and assign one to each Field Service equipment, so similar equipment can be grouped and classified.
This module adds a simple classification system for Field Service equipment. You can maintain a catalogue of equipment types, each with a name, a code, a free-text description and an active/archived status.
Where it appears in Odoo: - A new "Equipment Types" menu is added under the Field Service configuration area, opening a list and form to manage the types. - On the standard Field Service equipment form, a new "Type" field is added right after the owner field, so each equipment record can be linked to one type.
Business rules and behaviours: - Name and code are mandatory when creating an equipment type. - New types are active by default; the form has Archive and Restore buttons to hide or bring back a type without deleting it. - Access is controlled: regular Field Service users can only read equipment types, while Field Service managers can create, edit and delete them.
Areas touched: the module extends the existing fsm.equipment model with a link to the new fsm.equipment.type model, and adds the corresponding list, form and menu entries. No automatic computations, emails or scheduled jobs are included.
Depends on
Menus it adds
Models and fields (2)
- fsm.equipment · extends an existing modeltype_id
- fsm.equipment.type · new modelcode, name, active, description
Text generated by AI (DeepSeek) from reading the Odoo 14.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: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 14.0
Confirmed on 2026-11-03 in branch 14.0 of OCA/field-service.
terminal Installation and usage
No verified informationInstallation 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.