Field Service Management (FSM) coordinates company resources employed at, or en route to, client sites, rather than on the company's premises. FSM most commonly refers to companies who need to manage installation, service or repairs of systems or equipment.
Examples of field service use cases are:
- In telecommunications and cable industry, technicians who install cable or run phone lines into residences or business establishments.
- In healthcare, mobile nurses who provide in-home care for elderly or disabled.
- In gas utilities, engineers who are dispatched to investigate and repair suspected leaks.
- In heavy engineering, mining, industrial and manufacturing, technicians dispatched for preventative maintenance and repair.
- In property maintenance, including landscaping, irrigation, and home and office cleaning.
- In HVAC industry, technicians have the expertise and equipment to investigate units in residential, commercial and industrial environments.
| addon | version | maintainers | summary |
|---|---|---|---|
| base_territory | 17.0.1.0.0 |   |
This module allows you to define territories, branches, districts and regions to be used for Field Service operations or Sales. |
| fieldservice | 17.0.1.2.0 | |
Manage Field Service Locations, Workers and Orders |
| fieldservice_account | 17.0.1.0.0 |   |
Track invoices linked to Field Service orders |
| fieldservice_account_analytic | 17.0.1.0.0 | |
Track analytic accounts on Field Service locations and orders |
| fieldservice_activity | 17.0.1.0.0 |  |
Field Service Activities are a set of actions that need to be performed on a service order |
| fieldservice_calendar | 17.0.1.0.0 |  |
Add calendar to FSM Orders |
| fieldservice_crm | 17.0.1.0.0 |  |
Create Field Service orders from the CRM |
| fieldservice_equipment_stock | 17.0.1.0.0 |   |
Integrate stock operations with your field service equipments |
| fieldservice_geoengine | 17.0.1.0.0 | |
Display Field Service locations on a map with Open Street Map |
| fieldservice_isp_flow | 17.0.1.0.0 | |
Field Service workflow for Internet Service Providers |
| fieldservice_project | 17.0.1.0.0 | Create field service orders from a project or project task | |
| fieldservice_recurring | 17.0.1.1.0 | |
Manage recurring Field Service orders |
| fieldservice_repair | 17.0.1.0.0 | |
Integrate Field Service orders with MRP repair orders |
| fieldservice_route | 17.0.1.0.0 | |
Organize the routes of each day. |
| fieldservice_sale | 17.0.1.0.0 | |
Sell field services. |
| fieldservice_sale_recurring | 17.0.1.0.0 | |
Sell recurring field services. |
| fieldservice_sale_stock | 17.0.1.0.0 | |
Sell stockable items linked to field service orders. |
| fieldservice_size | 17.0.1.0.0 | |
Manage Sizes for Field Service Locations and Orders |
| fieldservice_stage_server_action | 17.0.1.1.0 | |
Execute server actions when reaching a Field Service stage |
| fieldservice_stage_validation | 17.0.1.0.0 | |
Validate input data when reaching a Field Service stage |
| fieldservice_stock | 17.0.1.0.0 | |
Integrate the logistics operations with Field Service |
| fieldservice_stock_request | 17.0.1.0.0 | |
Integrate Stock Requests with Field Service Orders |
| fieldservice_vehicle | 17.0.1.0.0 | |
Manage Field Service vehicles and assign drivers |
This repository is licensed under AGPL-3.0.
However, each module can have a totally different license, as long as they adhere to Odoo Community Association (OCA)
policy. Consult each module's __manifest__.py file, which contains a license key
that explains its license.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.