Package: odoo-addon-fieldservice
This module is the base of the Field Service application in Odoo.Table of contentsConfigurationOrder StagesField Service AreasSetup a TerritorySetup Branches, Districts, and RegionsAdvanced ConfigurationsManage TeamsManage CategoriesManage TagsManage Order TemplatesUsageAdd Field Service LocationsAdd Field Service WorkersProcess OrdersKnown issues / RoadmapBug TrackerCreditsAuthorsContributorsOther creditsMaintainersConfigurationThe 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 StagesThe 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 toField Service > Configuration > StagesCreate or edit a stageSet the name for the stage.Set the sequence order for the stage.SelectOrdertype to apply this stage to your orders.Additonally, you can set a color for the stage.Field Service AreasYou 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 TerritoryGo to Settings > Users & Companies > Territories*Create or select a territorySet the territory Name and descriptionSelect or create a branch which this territory servesChoose a type of zip, country whichs defines the boundary usedInput a list of zip codes, countries based on your desired
configurationSetup Branches, Districts, and RegionsIf your business requires, define your Branches, Districts, and Regions.
These are found underField Service > Configuration > LocationsAdvanced ConfigurationsAdditional features, automations, and GeoEngine features can be enabled
in the General Settings panel for Field Service.Go toField Service > Configuration > SettingsEnable additional optionsConfigure new optionsManage TeamsTeams 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 toField Service > Configuration > Workers > TeamsCreate or select a teamSet the team name, description, and sequenceYou can now define custom stages for each team processing orders.Go toField Service > Configuration > StagesCreate or edit a stageSelect the teams for which this stage should be usedManage CategoriesCategories are used to group workers and the type of orders a worker can
do.Go toField Service > Configuration > Workers > CategoriesCreate or select a categorySet the name and description of categoryAdditionally, you can select a parent category if requiredManage TagsTags can be used to filter and report on field service ordersGo toField Service > Configuration > Orders > TagsCreate or select a tagSet the tag nameSet a color index for the tagManage Order TemplatesOrder templates allow you to create standard templates for your orders.Go toField Service > Master Data > TemplatesCreate or select a templateSet the nameSet the standard order instructionsUsageTo use this module, you need to:Add Field Service LocationsLocations are the specific places where a field service order is
performed.Go toField Service > Master Data > LocationsCreate a locationAdd Field Service WorkersWorkers are the people responsible for performing a field service order.
These workers may be subcontractors or a company’s own employees.Go toField Service > Master Data > WorkersCreate a workerProcess OrdersOnce you have established your data, you can begin processing field
service orders.Go toField Service > Dashboard > OrdersCreate or select an orderEnter relevant details for the orderProcess order through each stage as defined by your business
requirementsKnown issues / RoadmapThe roadmap of the Field Service application is documented onGithub.Bug TrackerBugs are tracked onGitHub 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 welcomedfeedback.Do not contact contributors directly about support or help with technical issues.CreditsAuthorsOpen Source IntegratorsContributorsWolfgang 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>Ammar Officewala <ammar.o.serpentcs@gmail.com>Yves Goldberg <yves@ygol.com>Freni Patel <fpatel@opensourceintegrators.com>Tecnativa:Víctor MartínezNils Coenen <nils.coenen@nico-solutions.de>Alex Comba <alex.comba@agilebg.com>Other creditsThe development of this module has been financially supported by:Open Source Integrators <https://opensourceintegrators.com>MaintainersThis 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.Currentmaintainers:This module is part of theOCA/field-serviceproject on GitHub.You are welcome to contribute. To learn how please visithttps://odoo-community.org/page/Contribute.