Manage Field Service Locations, Workers and Orders
Project description
This module is the base of the Field Service application in Odoo.
Table of contents
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.
Go to Field Service > Configuration > Stages
Create or edit a stage
Set the name for the stage.
Set the sequence order for the stage.
Select Order type to apply this stage to your orders.
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
Go to Settings > Users & Companies > Territories*
Create or select a territory
Set the territory Name and description
Select or create a branch which this territory serves
Choose a type of zip, country whichs defines the boundary used
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.
Go to Field Service > Configuration > Settings
Enable additional options
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.
Go to Field Service > Configuration > Workers > Teams
Create or select a team
Set the team name, description, and sequence
You can now define custom stages for each team processing orders.
Go to Field Service > Configuration > Stages
Create or edit a stage
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.
Go to Field Service > Configuration > Workers > Categories
Create or select a category
Set the name and description of category
Additionally, you can select a parent category if required
Manage Order Templates
Order templates allow you to create standard templates for your orders.
Go to Field Service > Master Data > Templates
Create or select a template
Set the name
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.
Go to Field Service > Master Data > Locations
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.
Go to Field Service > Master Data > Workers
Create a worker
Process Orders
Once you have established your data, you can begin processing field service orders.
Go to Field Service > Dashboard > Orders
Create or select an order
Enter relevant details for the order
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.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Wolfgang Hall <whall@opensourceintegrators.com>
Maxime Chambreuil <mchambreuil@opensourceintegrators.com>
Steve Campbell <scampbell@opensourceintegrators.com>
Bhavesh Odedra <bodedra@opensourceintegrators.com>
Michael Allen <mallen@opensourceintegrators.com>
Sandip Mangukiya <smangukiya@opensourceintegrators.com>
Serpent Consulting Services Pvt. Ltd. <support@serpentcs.com>
Brian McMaster <brian@mcmpest.com>
Raphaël Reverdy <raphael.reverdy@akretion.com>
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.
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.
Current maintainers:
This module is part of the OCA/field-service project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distributions
Built Distribution
File details
Details for the file odoo13_addon_fieldservice-13.0.1.2.1-py3-none-any.whl
.
File metadata
- Download URL: odoo13_addon_fieldservice-13.0.1.2.1-py3-none-any.whl
- Upload date:
- Size: 285.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.1 CPython/3.8.5
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 973e81fe2f41323e1486600bfbf7f310633ce721fdcf5103bd1b7c7313981b68 |
|
MD5 | 9db6e668fb1e7e1bf30fceeed7b46fd8 |
|
BLAKE2b-256 | 9fc1540b758c50304d389a2a63d1950d3b21d15565601838fed0cec43a67a05f |