odoo-addon-fieldservice

============= Field Service

.. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! This file is generated by oca-gen-addon-readme !! !! changes will be overwritten. !! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !! source digest: sha256:ffab1ec59149ad1f3ae402cbbc3dcf330af32e4d971e498b3b2fcf487fcb200a !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

.. |badge1| image:: https://img.shields.io/badge/maturity-Production%2FStable-green.png :target: https://odoo-community.org/page/development-status :alt: Production/Stable .. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html :alt: License: AGPL-3 .. |badge3| image:: https://img.shields.io/badge/github-OCA%2Ffield--service-lightgray.png?logo=github :target: https://github.com/OCA/field-service/tree/18.0/fieldservice :alt: OCA/field-service .. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png :target: https://translation.odoo-community.org/projects/field-service-18-0/field-service-18-0-fieldservice :alt: Translate me on Weblate .. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png :target: https://runboat.odoo-community.org/builds?repo=OCA/field-service&target_branch=18.0 :alt: Try me on Runboat

|badge1| |badge2| |badge3| |badge4| |badge5|

This module is the base of the Field Service application in Odoo.

Table of contents

.. contents:: :local:

Configuration

The base Field Service module can be used with minimal initial configuration. It also allows for many advanced features, which require a more in-depth configuration.

Order Stages

The stage of an order is used to monitor its progress. Stages can be configured based on your company's specific business needs. A basic set of order stages comes pre-configured for use.

1. Go to Field Service > Configuration > Stages
2. Create or edit a stage
3. Set the name for the stage.
4. Set the sequence order for the stage.
5. Select Order type to apply this stage to your orders.
6. Additonally, you can set a color for the stage.

Field Service Areas

You can manage designated areas or locales for your field service workers, salesmen, and other resources. For example, salesmen may serve a particular Territory. There may be multiple Territories served by a single Branch office location. Multiple Branches are managed within a District and these Districts are managed under an encompassing Region.

Setup a Territory

1. Go to Settings > Users & Companies > Territories\*
2. Create or select a territory
3. Set the territory Name and description
4. Select or create a branch which this territory serves
5. Choose a type of zip, country whichs defines the boundary used
6. Input a list of zip codes, countries based on your desired
   configuration

Setup Branches, Districts, and Regions

If your business requires, define your Branches, Districts, and Regions. These are found under Field Service > Configuration > Locations

Advanced Configurations

Additional features, automations, and GeoEngine features can be enabled in the General Settings panel for Field Service.

1. Go to Field Service > Configuration > Settings
2. Enable additional options
3. Configure new options

Manage Teams

Teams can be used to organize the processing of field service orders
into groups. Different teams may have different workflows that a field
service order needs to follow.

1. Go to *Field Service > Configuration > Workers > Teams*
2. Create or select a team
3. Set the team name, description, and sequence

You can now define custom stages for each team processing orders.

1. Go to *Field Service > Configuration > Stages*
2. Create or edit a stage
3. Select the teams for which this stage should be used

Manage Categories

Categories are used to group workers and the type of orders a worker can do.

1. Go to Field Service > Configuration > Workers > Categories
2. Create or select a category
3. Set the name and description of category
4. Additionally, you can select a parent category if required

Manage Tags

Tags can be used to filter and report on field service orders

1. Go to *Field Service > Configuration > Orders > Tags*
2. Create or select a tag
3. Set the tag name
4. Set a color index for the tag

Manage Order Templates

Order templates allow you to create standard templates for your orders.

1. Go to Field Service > Master Data > Templates
2. Create or select a template
3. Set the name
4. Set the standard order instructions

Usage

To use this module, you need to:

Add Field Service Locations

Locations are the specific places where a field service order is performed.

1. Go to Field Service > Master Data > Locations
2. Create a location

Add Field Service Workers

Workers are the people responsible for performing a field service order. These workers may be subcontractors or a company's own employees.

1. Go to Field Service > Master Data > Workers
2. Create a worker

Process Orders

Once you have established your data, you can begin processing field service orders.

1. Go to Field Service > Dashboard > Orders
2. Create or select an order
3. Enter relevant details for the order
4. Process order through each stage as defined by your business requirements

Known issues / Roadmap

The roadmap of the Field Service application is documented on Github <https://github.com/OCA/field-service/issues/1>__.

Bug Tracker

Bugs are tracked on GitHub Issues <https://github.com/OCA/field-service/issues>. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback <https://github.com/OCA/field-service/issues/new?body=module:%20fieldservice%0Aversion:%2018.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• Open Source Integrators

Contributors

• Wolfgang Hall [e-mail]

• Maxime Chambreuil [e-mail]

• Steve Campbell [e-mail]

• Bhavesh Odedra [e-mail]

• Michael Allen [e-mail]

• Sandip Mangukiya [e-mail]

• Serpent Consulting Services Pvt. Ltd. [e-mail]

• Brian McMaster [e-mail]

• Raphaël Reverdy [e-mail]

• Ammar Officewala [e-mail]

• Yves Goldberg [e-mail]

• Freni Patel [e-mail]

• Tecnativa <https://www.tecnativa.com>__:

  • Víctor Martínez

• Nils Coenen [e-mail]

• Alex Comba [e-mail]

Other credits

The development of this module has been financially supported by:

• Open Source Integrators https://opensourceintegrators.com

Maintainers

This module is maintained by the OCA.

.. image:: https://odoo-community.org/logo.png :alt: Odoo Community Association :target: https://odoo-community.org

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.

.. |maintainer-max3903| image:: https://github.com/max3903.png?size=40px :target: https://github.com/max3903 :alt: max3903 .. |maintainer-brian10048| image:: https://github.com/brian10048.png?size=40px :target: https://github.com/brian10048 :alt: brian10048

Current maintainers <https://odoo-community.org/page/maintainer-role>__:

|maintainer-max3903| |maintainer-brian10048|

This module is part of the OCA/field-service <https://github.com/OCA/field-service/tree/18.0/fieldservice>_ project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.