Field Service - Maintenance
Odoo Maintenance App does not support Field Service operations for equipments outside the company facilities. On the other hand, the Field Service App does not support a maintenance schedule generating preventive maintenance request.
This module allows you to merge equipments from Field Service and Maintenance and have a maintenance schedule for FSM equipments as well as Field Service capabilities for maintenance equipments.
Table of contents
Installation
To install Field Service and have the mapping features, you need to install fieldservice_stock and maintenance
Please refer to the installation instructions available at: https://github.com/OCA/field-service/tree/11.0/fieldservice_maintenance
Configuration
To use this module, you need to:
Go to Field Service > Master Data > Equipments or Maintenance > Equipments
Create or select an equipment
Specify the maintenance schedule
Usage
To use this module, you need to:
Maintenance requests related to a FSM equipment will create a FSM order
Go to Field Service
Create or select a FSM order and select the type Maintenance.
Select the maintenance team, the equipment and the location
Upon saving, a maintenance request will be created with the information from the FSM order.
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
Sandip Mangukiya <smangukiya@opensourceintegrators.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.
Metadata
Release files for odoo11-addon-fieldservice-maintenance 11.0.0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo11_addon_fieldservice_maintenance-11.0.0.2.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for odoo11_addon_fieldservice_maintenance-11.0.0.2.0-py2.py3-none-any.whl |
Release files / odoo11_addon_fieldservice_maintenance-11.0.0.2.0-py2.py3-none-any.whl
| Download URL | odoo11_addon_fieldservice_maintenance-11.0.0.2.0-py2.py3-none-any.whl |
|---|---|
| Size | 34.8 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
f7c5a8ce4e71c4ef95face8e97cf1485425f0ee2d50af793963a17b436b71425
|
|
BLAKE2b-256 checksum How to use checksums |
5635f6c5a3439444ef1c4e3d96f7efc1143dd2a82c5bc1dccba77ce5c850e369
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo11-addon-fieldservice-maintenance 11.0.0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.